Beam Failure Recovery Procedures

ABSTRACT

Beam failure recovery (BFR) procedures are described for wireless communications. A base station may send a message to a wireless device during a BFR procedure. The message may comprise one or more BFR configuration parameters and/or reconfigure one or more BFR configuration parameters. The wireless device may stop the BFR procedure, for example, after or in response to receiving the message from the base station. The wireless device may perform a second BFR procedure using one or more of the BFR configuration parameters received in the message.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/580,910, filed Sep. 24, 2019, which claims the benefit of U.S.Provisional Application No. 62/735,558, titled “Beam Failure RecoveryProcedure in New Radio” and filed on Sep. 24, 2018. The above-referencedapplications are hereby incorporated by reference in their entireties.

BACKGROUND

A base station and/or a wireless device may use a beam failure recovery(BFR) procedure based on detecting a beam failure. A BFR procedure mayinclude transmission of at least one control signal. The transmission ofthe at least one control signal, or other portion of the BFR procedure,may be unsuccessful and/or delayed, which may lead to undesirableoutcomes.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

BFR procedures are described. A wireless device may be configured for aBFR procedure based on configuration parameters transmitted by a basestation. A wireless device may transmit at least one signal (e.g., a BFRrequest) to facilitate BFR procedure. For example, a wireless device maytransmit at least one signal to facilitate BFR based on the wirelessdevice detecting a beam failure. A wireless device may receive one ormore messages from the base station, for example, while waiting for aBFR response to the BFR request. The one or more messages may compriseand/or reconfigure one or more BFR configuration parameters. Thewireless device may stop the BFR recovery and initiate a new BFRprocedure, for example, after or in response to receiving the one ormore messages from the base station. The wireless device may receive aBFR response from the base station, for example, after or in response toinitiating the new BFR procedure. By stopping an initial BFR procedure,and initiating a second BFR procedure, the wireless device may recoverfrom the beam failure more quickly and/or consume less power whilerecovering from a beam failure.

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows an example radio access network (RAN) architecture.

FIG. 2A shows an example user plane protocol stack.

FIG. 2B shows an example control plane protocol stack.

FIG. 3 shows an example wireless device and two base stations.

FIG. 4A, FIG. 4B, FIG. 4C, and FIG. 4D show examples of uplink anddownlink signal transmission.

FIG. 5A shows an example uplink channel mapping and example uplinkphysical signals.

FIG. 5B shows an example downlink channel mapping and example downlinkphysical signals.

FIG. 6 shows an example transmission time and/or reception time for acarrier.

FIG. 7A and FIG. 7B show example sets of orthogonal frequency divisionmultiplexing (OFDM) subcarriers.

FIG. 8 shows example OFDM radio resources.

FIG. 9A shows an example channel state information reference signal(CSI-RS) and/or synchronization signal (SS) block transmission in amulti-beam system.

FIG. 9B shows an example downlink beam management procedure.

FIG. 10 shows an example of configured bandwidth parts (BWPs).

FIG. 11A and FIG. 11B show examples of multi connectivity.

FIG. 12 shows an example of a random access procedure.

FIG. 13 shows example medium access control (MAC) entities.

FIG. 14 shows an example RAN architecture.

FIG. 15 shows example radio resource control (RRC) states.

FIG. 16A and FIG. 16B show examples of beam failure scenarios.

FIG. 17 shows an example of a beam failure recovery (BFR) procedure.

FIG. 18 shows an example of downlink beam failure instance indication.

FIG. 19 shows an example of BWP operation.

FIG. 20 shows an example of BWP operation in an SCell.

FIG. 21A and FIG. 21B show an example of a system for a random accessprocedure using BWP switching.

FIG. 22 shows an example method for BWP switching for a random accessprocedure.

FIG. 23 shows an example of a BWP linkage in beam failure recoveryprocedure.

FIG. 24 shows an example of a BWP linkage in beam failure recoveryprocedure.

FIG. 25 shows an example of a downlink beam failure recovery procedure.

FIG. 26 shows an example of a downlink beam failure recovery procedure.

FIG. 27 shows an example flowchart of a downlink beam failure recoveryprocedure.

FIG. 28 shows an example flowchart of a downlink beam failure recoveryprocedure.

FIG. 29 shows an example of a downlink beam failure recovery procedure.

FIG. 30 shows an example of a downlink beam failure recovery procedure.

FIG. 31 shows an example flowchart of a beam failure recovery procedure.

FIG. 32 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings and descriptions provide examples. It is to beunderstood that the examples shown in the drawings and/or described arenon-exclusive and that there are other examples of how features shownand described may be practiced.

Examples are provided for operation of wireless communication systemswhich may be used in the technical field of multicarrier communicationsystems. More particularly, the technology described herein may relateto beam failure recovery procedures in multicarrier communicationsystems.

The following acronyms are used throughout the drawings and/ordescriptions, and are provided below for convenience although otheracronyms may be introduced in the detailed description:

3GPP 3rd Generation Partnership Project

5GC 5G Core Network

ACK Acknowledgement

AMF Access and Mobility Management Function

ARQ Automatic Repeat Request

AS Access Stratum

ASIC Application-Specific Integrated Circuit

BA Bandwidth Adaptation

BCCH Broadcast Control Channel

BCH Broadcast Channel

BFR Beam Failure Recovery

BLER Block Error Rate

BPSK Binary Phase Shift Keying

BSR Buffer Status Report

BWP Bandwidth Part

CA Carrier Aggregation

CC Component Carrier

CCCH Common Control CHannel

CDMA Code Division Multiple Access

CN Core Network

CORESET Control Resource Set

CP Cyclic Prefix

CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex

C-RNTI Cell-Radio Network Temporary Identifier

CS Configured Scheduling

CSI Channel State Information

CSI-RS Channel State Information-Reference Signal

CQI Channel Quality Indicator

CSS Common Search Space

CU Central Unit

DC Dual Connectivity

DCCH Dedicated Control Channel

DCI Downlink Control Information

DL Downlink

DL-SCH Downlink Shared CHannel

DM-RS DeModulation Reference Signal

DRB Data Radio Bearer

DRX Discontinuous Reception

DTCH Dedicated Traffic Channel

DU Distributed Unit

EPC Evolved Packet Core

E-UTRA Evolved UMTS Terrestrial Radio Access

E-UTRAN Evolved-Universal Terrestrial Radio Access Network

FDD Frequency Division Duplex

FPGA Field Programmable Gate Arrays

F1-C F1-Control plane

F1-U F1-User plane

gNB next generation Node B

HARQ Hybrid Automatic Repeat reQuest

HDL Hardware Description Languages

IE Information Element

IP Internet Protocol

LCH Logical Channel

LCID Logical Channel Identifier

LTE Long Term Evolution

MAC Medium Access Control

MCG Master Cell Group

MCS Modulation and Coding Scheme

MeNB Master evolved Node B

MIB Master Information Block

MME Mobility Management Entity

MN Master Node

NACK Negative Acknowledgement

NAS Non-Access Stratum

NG CP Next Generation Control Plane

NGC Next Generation Core

NG-C NG-Control plane

ng-eNB next generation evolved Node B

NG-U NG-User plane

NR New Radio

NR MAC New Radio MAC

NR PDCP New Radio PDCP

NR PHY New Radio PHYsical

NR RLC New Radio RLC

NR RRC New Radio RRC

NSSAI Network Slice Selection Assistance Information

O&M Operation and Maintenance

OFDM Orthogonal Frequency Division Multiplexing

PBCH Physical Broadcast CHannel

PCC Primary Component Carrier

PCCH Paging Control CHannel

PCell Primary Cell

PCH Paging CHannel

PDCCH Physical Downlink Control CHannel

PDCP Packet Data Convergence Protocol

PDSCH Physical Downlink Shared CHannel

PDU Protocol Data Unit

PHICH Physical HARQ Indicator CHannel

PHY PHYsical

PLMN Public Land Mobile Network

PMI Precoding Matrix Indicator

PRACH Physical Random Access CHannel

PRB Physical Resource Block

PSCell Primary Secondary Cell

PSS Primary Synchronization Signal

pTAG primary Timing Advance Group

PT-RS Phase Tracking Reference Signal

PUCCH Physical Uplink Control CHannel

PUSCH Physical Uplink Shared CHannel

QAM Quadrature Amplitude Modulation

QCLed Quasi-Co-Located

QCL Quasi-Co-Location

QFI Quality of Service Indicator

QoS Quality of Service

QPSK Quadrature Phase Shift Keying

RA Random Access

RACH Random Access CHannel

RAN Radio Access Network

RAT Radio Access Technology

RA-RNTI Random Access-Radio Network Temporary Identifier

RB Resource Blocks

RBG Resource Block Groups

RI Rank indicator

RLC Radio Link Control

RLM Radio Link Monitoring

RRC Radio Resource Control

RS Reference Signal

RSRP Reference Signal Received Power

SCC Secondary Component Carrier

SCell Secondary Cell

SCG Secondary Cell Group

SC-FDMA Single Carrier-Frequency Division Multiple Access

SDAP Service Data Adaptation Protocol

SDU Service Data Unit

SeNB Secondary evolved Node B

SFN System Frame Number

S-GW Serving GateWay

SI System Information

SIB System Information Block

SINR Signal-to-Interference-plus-Noise Ratio

SMF Session Management Function

SN Secondary Node

SpCell Special Cell

SR Scheduling Request

SRB Signaling Radio Bearer

SRS Sounding Reference Signal

SS Synchronization Signal

SSB Synchronization Signal Block

SSS Secondary Synchronization Signal

sTAG secondary Timing Advance Group

TA Timing Advance

TAG Timing Advance Group

TAI Tracking Area Identifier

TAT Time Alignment Timer

TB Transport Block

TC-RNTI Temporary Cell-Radio Network Temporary Identifier

TCI Transmission Configuration Indication

TDD Time Division Duplex

TDMA Time Division Multiple Access

TRP Transmission and Receiving Point

TTI Transmission Time Interval

UCI Uplink Control Information

UE User Equipment

UL Uplink

UL-SCH Uplink Shared CHannel

UPF User Plane Function

UPGW User Plane Gateway

VHDL VHSIC Hardware Description Language

Xn-C Xn-Control plane

Xn-U Xn-User plane

Examples described herein may be implemented using various physicallayer modulation and transmission mechanisms. Example transmissionmechanisms may include, but are not limited to: Code Division MultipleAccess (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA),Time Division Multiple Access (TDMA), Wavelet technologies, and/or thelike. Hybrid transmission mechanisms such as TDMA/CDMA, and/or OFDM/CDMAmay be used. Various modulation schemes may be used for signaltransmission in the physical layer. Examples of modulation schemesinclude, but are not limited to: phase, amplitude, code, a combinationof these, and/or the like. An example radio transmission method mayimplement Quadrature Amplitude Modulation (QAM) using Binary Phase ShiftKeying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM,256-QAM, 1024-QAM and/or the like. Physical radio transmission may beenhanced by dynamically or semi-dynamically changing the modulation andcoding scheme, for example, depending on transmission requirementsand/or radio conditions.

FIG. 1 shows an example Radio Access Network (RAN) architecture. A RANnode may comprise a next generation Node B (gNB) (e.g., 120A, 120B)providing New Radio (NR) user plane and control plane protocolterminations towards a first wireless device (e.g., 110A). A RAN nodemay comprise a base station such as a next generation evolved Node B(ng-eNB) (e.g., 120C, 120D), providing Evolved UMTS Terrestrial RadioAccess (E-UTRA) user plane and control plane protocol terminationstowards a second wireless device (e.g., 110B). A first wireless device110A may communicate with a base station, such as a gNB 120A, over a Uuinterface. A second wireless device 110B may communicate with a basestation, such as an ng-eNB 120D, over a Uu interface. The wirelessdevices 110A and/or 110B may be structurally similar to wireless devicesshown in and/or described in connection with other drawing figures. TheNode B 120A, the Node B 120B, the Node B 120C, and/or the Node B 120Dmay be structurally similar to Nodes B and/or base stations shown inand/or described in connection with other drawing figures.

A base station, such as a gNB (e.g., 120A, 120B, etc.) and/or an ng-eNB(e.g., 120C, 120D, etc.) may host functions such as radio resourcemanagement and scheduling, IP header compression, encryption andintegrity protection of data, selection of Access and MobilityManagement Function (AMF) at wireless device (e.g., User Equipment (UE))attachment, routing of user plane and control plane data, connectionsetup and release, scheduling and transmission of paging messages (e.g.,originated from the AMF), scheduling and transmission of systembroadcast information (e.g., originated from the AMF or Operation andMaintenance (O&M)), measurement and measurement reporting configuration,transport level packet marking in the uplink, session management,support of network slicing, Quality of Service (QoS) flow management andmapping to data radio bearers, support of wireless devices in aninactive state (e.g., RRC_INACTIVE state), distribution function forNon-Access Stratum (NAS) messages, RAN sharing, dual connectivity,and/or tight interworking between NR and E-UTRA.

One or more first base stations (e.g., gNBs 120A and 120B) and/or one ormore second base stations (e.g., ng-eNBs 120C and 120D) may beinterconnected with each other via Xn interface. A first base station(e.g., gNB 120A, 120B, etc.) or a second base station (e.g., ng-eNB120C, 120D, etc.) may be connected via NG interfaces to a network, suchas a 5G Core Network (5GC). A 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g., 130A and/or 130B). A base station (e.g.,a gNB and/or an ng-eNB) may be connected to a UPF via an NG-User plane(NG-U) interface. The NG-U interface may provide delivery (e.g.,non-guaranteed delivery) of user plane Protocol Data Units (PDUs)between a RAN node and the UPF. A base station (e.g., a gNB and/or anng-eNB) may be connected to an AMF via an NG-Control plane (NG-C)interface. The NG-C interface may provide functions such as NG interfacemanagement, wireless device (e.g., UE) context management, wirelessdevice (e.g., UE) mobility management, transport of NAS messages,paging, PDU session management, configuration transfer, and/or warningmessage transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (e.g., if applicable), external PDUsession point of interconnect to data network, packet routing andforwarding, packet inspection and user plane part of policy ruleenforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, quality of service (QoS) handling for userplane, packet filtering, gating, Uplink (UL)/Downlink (DL) rateenforcement, uplink traffic verification (e.g., Service Data Flow (SDF)to QoS flow mapping), downlink packet buffering, and/or downlink datanotification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling (e.g., for mobility between 3rd GenerationPartnership Project (3GPP) access networks), idle mode wireless devicereachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (e.g., subscription and/orpolicies), support of network slicing, and/or Session ManagementFunction (SMF) selection.

FIG. 2A shows an example user plane protocol stack. A Service DataAdaptation Protocol (SDAP) (e.g., 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g., 212 and 222), Radio Link Control (RLC) (e.g., 213and 223), and Medium Access Control (MAC) (e.g., 214 and 224) sublayers,and a Physical (PHY) (e.g., 215 and 225) layer, may be terminated in awireless device (e.g., 110) and in a base station (e.g., 120) on anetwork side. A PHY layer may provide transport services to higherlayers (e.g., MAC, RRC, etc.). Services and/or functions of a MACsublayer may comprise mapping between logical channels and transportchannels, multiplexing and/or demultiplexing of MAC Service Data Units(SDUs) belonging to the same or different logical channels into and/orfrom Transport Blocks (TBs) delivered to and/or from the PHY layer,scheduling information reporting, error correction through HybridAutomatic Repeat request (HARQ) (e.g., one HARQ entity per carrier forCarrier Aggregation (CA)), priority handling between wireless devicessuch as by using dynamic scheduling, priority handling between logicalchannels of a wireless device such as by using logical channelprioritization, and/or padding. A wireless device (e.g., a MAC entity ofthe wireless device) may support one or multiple numerologies and/ortransmission timings. Mapping restrictions in a logical channelprioritization may control which numerology and/or transmission timing alogical channel may use. An RLC sublayer may support transparent mode(TM), unacknowledged mode (UM), and/or acknowledged mode (AM)transmission modes. The RLC configuration may be per logical channelwith no dependency on numerologies and/or Transmission Time Interval(TTI) durations. Automatic Repeat Request (ARQ) may operate on any ofthe numerologies and/or TTI durations with which the logical channel isconfigured. Services and functions of the PDCP layer for the user planemay comprise, for example, sequence numbering, header compression anddecompression, transfer of user data, reordering and duplicatedetection, PDCP PDU routing (e.g., such as for split bearers),retransmission of PDCP SDUs, ciphering, deciphering and integrityprotection, PDCP SDU discard, PDCP re-establishment and data recoveryfor RLC AM, and/or duplication of PDCP PDUs. Services and/or functionsof SDAP may comprise, for example, mapping between a QoS flow and a dataradio bearer. Services and/or functions of SDAP may comprise mapping aQuality of Service Indicator (QFI) in DL and UL packets. A protocolentity of SDAP may be configured for an individual PDU session.

FIG. 2B shows an example control plane protocol stack. A PDCP (e.g., 233and 242), RLC (e.g., 234 and 243), and MAC (e.g., 235 and 244)sublayers, and a PHY (e.g., 236 and 245) layer, may be terminated in awireless device (e.g., 110), and in a base station (e.g., 120) on anetwork side, and perform service and/or functions described above. RRC(e.g., 232 and 241) may be terminated in a wireless device and a basestation on a network side. Services and/or functions of RRC may comprisebroadcast of system information related to AS and/or NAS; paging (e.g.,initiated by a 5GC or a RAN); establishment, maintenance, and/or releaseof an RRC connection between the wireless device and RAN; securityfunctions such as key management, establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and DataRadio Bearers (DRBs); mobility functions; QoS management functions;wireless device measurement reporting and control of the reporting;detection of and recovery from radio link failure; and/or NAS messagetransfer to/from NAS from/to a wireless device. NAS control protocol(e.g., 231 and 251) may be terminated in the wireless device and AMF(e.g., 130) on a network side. NAS control protocol may performfunctions such as authentication, mobility management between a wirelessdevice and an AMF (e.g., for 3GPP access and non-3GPP access), and/orsession management between a wireless device and an SMF (e.g., for 3GPPaccess and non-3GPP access).

A base station may configure a plurality of logical channels for awireless device. A logical channel of the plurality of logical channelsmay correspond to a radio bearer. The radio bearer may be associatedwith a QoS requirement. A base station may configure a logical channelto be mapped to one or more TTIs and/or numerologies in a plurality ofTTIs and/or numerologies. The wireless device may receive DownlinkControl Information (DCI) via a Physical Downlink Control CHannel(PDCCH) indicating an uplink grant. The uplink grant may be for a firstTTI and/or a first numerology and may indicate uplink resources fortransmission of a transport block. The base station may configure eachlogical channel in the plurality of logical channels with one or moreparameters to be used by a logical channel prioritization procedure atthe MAC layer of the wireless device. The one or more parameters maycomprise, for example, priority, prioritized bit rate, etc. A logicalchannel in the plurality of logical channels may correspond to one ormore buffers comprising data associated with the logical channel. Thelogical channel prioritization procedure may allocate the uplinkresources to one or more first logical channels in the plurality oflogical channels and/or to one or more MAC Control Elements (CEs). Theone or more first logical channels may be mapped to the first TTI and/orthe first numerology. The MAC layer at the wireless device may multiplexone or more MAC CEs and/or one or more MAC SDUs (e.g., logical channel)in a MAC PDU (e.g., transport block). The MAC PDU may comprise a MACheader comprising a plurality of MAC sub-headers. A MAC sub-header inthe plurality of MAC sub-headers may correspond to a MAC CE or a MAC SUD(e.g., logical channel) in the one or more MAC CEs and/or in the one ormore MAC SDUs. A MAC CE and/or a logical channel may be configured witha Logical Channel IDentifier (LCID). An LCID for a logical channeland/or a MAC CE may be fixed and/or pre-configured. An LCID for alogical channel and/or MAC CE may be configured for the wireless deviceby the base station. The MAC sub-header corresponding to a MAC CE and/ora MAC SDU may comprise an LCID associated with the MAC CE and/or the MACSDU.

A base station may activate, deactivate, and/or impact one or moreprocesses (e.g., set values of one or more parameters of the one or moreprocesses or start and/or stop one or more timers of the one or moreprocesses) at the wireless device, for example, by using one or more MACcommands. The one or more MAC commands may comprise one or more MACcontrol elements. The one or more processes may comprise activationand/or deactivation of PDCP packet duplication for one or more radiobearers. The base station may send (e.g., transmit) a MAC CE comprisingone or more fields. The values of the fields may indicate activationand/or deactivation of PDCP duplication for the one or more radiobearers. The one or more processes may comprise Channel StateInformation (CSI) transmission of on one or more cells. The base stationmay send (e.g., transmit) one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells.The one or more processes may comprise activation and/or deactivation ofone or more secondary cells. The base station may send (e.g., transmit)a MAC CE indicating activation and/or deactivation of one or moresecondary cells. The base station may send (e.g., transmit) one or moreMAC CEs indicating starting and/or stopping of one or more DiscontinuousReception (DRX) timers at the wireless device. The base station may send(e.g., transmit) one or more MAC CEs that indicate one or more timingadvance values for one or more Timing Advance Groups (TAGs).

FIG. 3 shows an example of base stations (base station 1, 120A, and basestation 2, 120B) and a wireless device 110. The wireless device 110 maycomprise a UE or any other wireless device. The base station (e.g.,120A, 120B) may comprise a Node B, eNB, gNB, ng-eNB, or any other basestation. A wireless device and/or a base station may perform one or morefunctions of a relay node. The base station 1, 120A, may comprise atleast one communication interface 320A (e.g., a wireless modem, anantenna, a wired modem, and/or the like), at least one processor 321A,and at least one set of program code instructions 323A that may bestored in non-transitory memory 322A and executable by the at least oneprocessor 321A. The base station 2, 120B, may comprise at least onecommunication interface 320B, at least one processor 321B, and at leastone set of program code instructions 323B that may be stored innon-transitory memory 322B and executable by the at least one processor321B.

A base station may comprise any number of sectors, for example: 1, 2, 3,4, or 6 sectors. A base station may comprise any number of cells, forexample, ranging from 1 to 50 cells or more. A cell may be categorized,for example, as a primary cell or secondary cell. At Radio ResourceControl (RRC) connection establishment, re-establishment, handover,etc., a serving cell may provide NAS (non-access stratum) mobilityinformation (e.g., Tracking Area Identifier (TAI)). At RRC connectionre-establishment and/or handover, a serving cell may provide securityinput. This serving cell may be referred to as the Primary Cell (PCell).In the downlink, a carrier corresponding to the PCell may be a DLPrimary Component Carrier (PCC). In the uplink, a carrier may be an ULPCC. Secondary Cells (SCells) may be configured to form together with aPCell a set of serving cells, for example, depending on wireless devicecapabilities. In a downlink, a carrier corresponding to an SCell may bea downlink secondary component carrier (DL SCC). In an uplink, a carriermay be an uplink secondary component carrier (UL SCC). An SCell may ormay not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and/or a cell index. A carrier(downlink and/or uplink) may belong to one cell. The cell ID and/or cellindex may identify the downlink carrier and/or uplink carrier of thecell (e.g., depending on the context it is used). A cell ID may beequally referred to as a carrier ID, and a cell index may be referred toas a carrier index. A physical cell ID and/or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted via a downlink carrier. A cell index may bedetermined using RRC messages. A first physical cell ID for a firstdownlink carrier may indicate that the first physical cell ID is for acell comprising the first downlink carrier. The same concept may beused, for example, with carrier activation and/or deactivation (e.g.,secondary cell activation and/or deactivation). A first carrier that isactivated may indicate that a cell comprising the first carrier isactivated.

A base station may send (e.g., transmit) to a wireless device one ormore messages (e.g., RRC messages) comprising a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted and/or unicasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and/or NAS; paginginitiated by a 5GC and/or an NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and an NG-RAN,which may comprise at least one of addition, modification, and/orrelease of carrier aggregation; and/or addition, modification, and/orrelease of dual connectivity in NR or between E-UTRA and NR. Servicesand/or functions of an RRC sublayer may comprise at least one ofsecurity functions comprising key management; establishment,configuration, maintenance, and/or release of Signaling Radio Bearers(SRBs) and/or Data Radio Bearers (DRBs); mobility functions which maycomprise at least one of a handover (e.g., intra NR mobility orinter-RAT mobility) and/or a context transfer; and/or a wireless devicecell selection and/or reselection and/or control of cell selection andreselection. Services and/or functions of an RRC sublayer may compriseat least one of QoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; and/or NAS message transfer to and/or from a core networkentity (e.g., AMF, Mobility Management Entity (MME)) from and/or to thewireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state,and/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection and/or re-selection; monitoring and/or receiving a paging formobile terminated data initiated by 5GC; paging for mobile terminateddata area managed by 5GC; and/or DRX for CN paging configured via NAS.In an RRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection and/orre-selection; monitoring and/or receiving a RAN and/or CN paginginitiated by an NG-RAN and/or a 5GC; RAN-based notification area (RNA)managed by an NG-RAN; and/or DRX for a RAN and/or CN paging configuredby NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station(e.g., NG-RAN) may keep a 5GC-NG-RAN connection (e.g., both C/U-planes)for the wireless device; and/or store a wireless device AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g., NG-RAN) may perform at least one of: establishmentof 5GC-NG-RAN connection (both C/U-planes) for the wireless device;storing a UE AS context for the wireless device; send (e.g., transmit)and/or receive of unicast data to and/or from the wireless device;and/or network-controlled mobility based on measurement results receivedfrom the wireless device. In an RRC_Connected state of a wirelessdevice, an NG-RAN may know a cell to which the wireless device belongs.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and/or information foracquiring any other SI broadcast periodically and/or provisionedon-demand (e.g., scheduling information). The other SI may either bebroadcast, and/or be provisioned in a dedicated manner, such as eithertriggered by a network and/or upon request from a wireless device. Aminimum SI may be transmitted via two different downlink channels usingdifferent messages (e.g., MasterinformationBlock andSystemInformationBlockType1). Another SI may be transmitted viaSystemInformationBlockType2. For a wireless device in an RRC_Connectedstate, dedicated RRC signaling may be used for the request and deliveryof the other SI. For the wireless device in the RRC_Idle state and/or inthe RRC_Inactive state, the request may trigger a random accessprocedure.

A wireless device may report its radio access capability information,which may be static. A base station may request one or more indicationsof capabilities for a wireless device to report based on bandinformation. A temporary capability restriction request may be sent bythe wireless device (e.g., if allowed by a network) to signal thelimited availability of some capabilities (e.g., due to hardwaresharing, interference, and/or overheating) to the base station. The basestation may confirm or reject the request. The temporary capabilityrestriction may be transparent to 5GC (e.g., static capabilities may bestored in 5GC).

A wireless device may have an RRC connection with a network, forexample, if CA is configured. At RRC connection establishment,re-establishment, and/or handover procedures, a serving cell may provideNAS mobility information. At RRC connection re-establishment and/orhandover, a serving cell may provide a security input. This serving cellmay be referred to as the PCell. SCells may be configured to formtogether with the PCell a set of serving cells, for example, dependingon the capabilities of the wireless device. The configured set ofserving cells for the wireless device may comprise a PCell and one ormore SCells.

The reconfiguration, addition, and/or removal of SCells may be performedby RRC messaging. At intra-NR handover, RRC may add, remove, and/orreconfigure SCells for usage with the target PCell. Dedicated RRCsignaling may be used (e.g., if adding a new SCell) to send all requiredsystem information of the SCell (e.g., if in connected mode, wirelessdevices may not acquire broadcasted system information directly from theSCells).

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g., to establish, modify, and/or releaseRBs; to perform handover; to setup, modify, and/or release measurements,for example, to add, modify, and/or release SCells and cell groups). NASdedicated information may be transferred from the network to thewireless device, for example, as part of the RRC connectionreconfiguration procedure. The RRCConnectionReconfiguration message maybe a command to modify an RRC connection. One or more RRC messages mayconvey information for measurement configuration, mobility control,and/or radio resource configuration (e.g., RBs, MAC main configuration,and/or physical channel configuration), which may comprise anyassociated dedicated NAS information and/or security configuration. Thewireless device may perform an SCell release, for example, if thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList. The wireless device may perform SCell additions ormodification, for example, if the received RRC ConnectionReconfiguration message includes the sCellToAddModList.

An RRC connection establishment, reestablishment, and/or resumeprocedure may be to establish, reestablish, and/or resume an RRCconnection, respectively. An RRC connection establishment procedure maycomprise SRB1 establishment. The RRC connection establishment proceduremay be used to transfer the initial NAS dedicated information and/ormessage from a wireless device to an E-UTRAN. TheRRCConnectionReestablishment message may be used to re-establish SRB1.

A measurement report procedure may be used to transfer measurementresults from a wireless device to an NG-RAN. The wireless device mayinitiate a measurement report procedure, for example, after successfulsecurity activation. A measurement report message may be used to send(e.g., transmit) measurement results.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g., a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 that may be stored in non-transitory memory 315 andexecutable by the at least one processor 314. The wireless device 110may further comprise at least one of at least one speaker and/ormicrophone 311, at least one keypad 312, at least one display and/ortouchpad 313, at least one power source 317, at least one globalpositioning system (GPS) chipset 318, and/or other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and/or the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding and/or processing, dataprocessing, power control, input/output processing, and/or any otherfunctionality that may enable the wireless device 110, the base station1 120A and/or the base station 2 120B to operate in a wirelessenvironment.

The processor 314 of the wireless device 110 may be connected to and/orin communication with the speaker and/or microphone 311, the keypad 312,and/or the display and/or touchpad 313. The processor 314 may receiveuser input data from and/or provide user output data to the speakerand/or microphone 311, the keypad 312, and/or the display and/ortouchpad 313. The processor 314 in the wireless device 110 may receivepower from the power source 317 and/or may be configured to distributethe power to the other components in the wireless device 110. The powersource 317 may comprise at least one of one or more dry cell batteries,solar cells, fuel cells, and/or the like. The processor 314 may beconnected to the GPS chipset 318. The GPS chipset 318 may be configuredto provide geographic location information of the wireless device 110.

The processor 314 of the wireless device 110 may further be connected toand/or in communication with other peripherals 319, which may compriseone or more software and/or hardware modules that may provide additionalfeatures and/or functionalities. For example, the peripherals 319 maycomprise at least one of an accelerometer, a satellite transceiver, adigital camera, a universal serial bus (USB) port, a hands-free headset,a frequency modulated (FM) radio unit, a media player, an Internetbrowser, and/or the like.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110, for example, via a wireless link 330A and/or via awireless link 330B, respectively. The communication interface 320A ofthe base station 1, 120A, may communicate with the communicationinterface 320B of the base station 2 and/or other RAN and/or corenetwork nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110, and/or thebase station 2 120B and the wireless device 110, may be configured tosend and receive transport blocks, for example, via the wireless link330A and/or via the wireless link 330B, respectively. The wireless link330A and/or the wireless link 330B may use at least one frequencycarrier. Transceiver(s) may be used. A transceiver may be a device thatcomprises both a transmitter and a receiver. Transceivers may be used indevices such as wireless devices, base stations, relay nodes, computingdevices, and/or the like. Radio technology may be implemented in thecommunication interface 310, 320A, and/or 320B, and the wireless link330A and/or 330B. The radio technology may comprise one or more elementsshown in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6, FIG. 7A, FIG. 7B,FIG. 8, and associated text, described below.

Other nodes in a wireless network (e.g., AMF, UPF, SMF, etc.) maycomprise one or more communication interfaces, one or more processors,and memory storing instructions. A node (e.g., wireless device, basestation, AMF, SMF, UPF, servers, switches, antennas, and/or the like)may comprise one or more processors, and memory storing instructionsthat when executed by the one or more processors causes the node toperform certain processes and/or functions. Single-carrier and/ormulti-carrier communication operation may be performed. A non-transitorytangible computer readable media may comprise instructions executable byone or more processors to cause operation of single-carrier and/ormulti-carrier communications. An article of manufacture may comprise anon-transitory tangible computer readable machine-accessible mediumhaving instructions encoded thereon for enabling programmable hardwareto cause a node to enable operation of single-carrier and/ormulti-carrier communications. The node may include processors, memory,interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, and/or electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and/or code stored in(and/or in communication with) a memory device to implement connections,electronic device operations, protocol(s), protocol layers,communication drivers, device drivers, hardware operations, combinationsthereof, and/or the like.

A communication network may comprise the wireless device 110, the basestation 1, 120A, the base station 2, 120B, and/or any other device. Thecommunication network may comprise any number and/or type of devices,such as, for example, computing devices, wireless devices, mobiledevices, handsets, tablets, laptops, internet of things (IoT) devices,hotspots, cellular repeaters, computing devices, and/or, more generally,user equipment (e.g., UE). Although one or more of the above types ofdevices may be referenced herein (e.g., UE, wireless device, computingdevice, etc.), it should be understood that any device herein maycomprise any one or more of the above types of devices or similardevices. The communication network, and any other network referencedherein, may comprise an LTE network, a 5G network, or any other networkfor wireless communications. Apparatuses, systems, and/or methodsdescribed herein may generally be described as implemented on one ormore devices (e.g., wireless device, base station, eNB, gNB, computingdevice, etc.), in one or more networks, but it will be understood thatone or more features and steps may be implemented on any device and/orin any network. As used throughout, the term “base station” may compriseone or more of: a base station, a node, a Node B, a gNB, an eNB, anng-eNB, a relay node (e.g., an integrated access and backhaul (IAB)node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an accesspoint (e.g., a WiFi access point), a computing device, a device capableof wirelessly communicating, or any other device capable of sendingand/or receiving signals. As used throughout, the term “wireless device”may comprise one or more of: a UE, a handset, a mobile device, acomputing device, a node, a device capable of wirelessly communicating,or any other device capable of sending and/or receiving signals. Anyreference to one or more of these terms/devices also considers use ofany other term/device mentioned above.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink anddownlink signal transmission. FIG. 4A shows an example uplinktransmitter for at least one physical channel A baseband signalrepresenting a physical uplink shared channel may perform one or morefunctions. The one or more functions may comprise at least one of:scrambling (e.g., by Scrambling); modulation of scrambled bits togenerate complex-valued symbols (e.g., by a Modulation mapper); mappingof the complex-valued modulation symbols onto one or severaltransmission layers (e.g., by a Layer mapper); transform precoding togenerate complex-valued symbols (e.g., by a Transform precoder);precoding of the complex-valued symbols (e.g., by a Precoder); mappingof precoded complex-valued symbols to resource elements (e.g., by aResource element mapper); generation of complex-valued time-domainSingle Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDMsignal for an antenna port (e.g., by a signal gen.); and/or the like. ASC-FDMA signal for uplink transmission may be generated, for example, iftransform precoding is enabled. A CP-OFDM signal for uplink transmissionmay be generated by FIG. 4A, for example, if transform precoding is notenabled. These functions are shown as examples and other mechanisms maybe implemented.

FIG. 4B shows an example of modulation and up-conversion to the carrierfrequency of a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or for the complex-valued Physical Random AccessCHannel (PRACH) baseband signal. Filtering may be performed prior totransmission.

FIG. 4C shows an example of downlink transmissions. The baseband signalrepresenting a downlink physical channel may perform one or morefunctions. The one or more functions may comprise: scrambling of codedbits in a codeword to be transmitted on a physical channel (e.g., byScrambling); modulation of scrambled bits to generate complex-valuedmodulation symbols (e.g., by a Modulation mapper); mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers (e.g., by a Layer mapper); precoding of the complex-valuedmodulation symbols on a layer for transmission on the antenna ports(e.g., by Precoding); mapping of complex-valued modulation symbols foran antenna port to resource elements (e.g., by a Resource elementmapper); generation of complex-valued time-domain OFDM signal for anantenna port (e.g., by an OFDM signal gen.); and/or the like. Thesefunctions are shown as examples and other mechanisms may be implemented.

A base station may send (e.g., transmit) a first symbol and a secondsymbol on an antenna port, to a wireless device. The wireless device mayinfer the channel (e.g., fading gain, multipath delay, etc.) forconveying the second symbol on the antenna port, from the channel forconveying the first symbol on the antenna port. A first antenna port anda second antenna port may be quasi co-located, for example, if one ormore large-scale properties of the channel over which a first symbol onthe first antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;Doppler spread; Doppler shift; average gain; average delay; and/orspatial receiving (Rx) parameters.

FIG. 4D shows an example modulation and up-conversion to the carrierfrequency of the complex-valued OFDM baseband signal for an antennaport. Filtering may be performed prior to transmission.

FIG. 5A shows example uplink channel mapping and example uplink physicalsignals. A physical layer may provide one or more information transferservices to a MAC and/or one or more higher layers. The physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and/or with what characteristics data is transferred overthe radio interface.

Uplink transport channels may comprise an Uplink-Shared CHannel (UL-SCH)501 and/or a Random Access CHannel (RACH) 502. A wireless device maysend (e.g., transmit) one or more uplink DM-RSs 506 to a base stationfor channel estimation, for example, for coherent demodulation of one ormore uplink physical channels (e.g., PUSCH 503 and/or PUCCH 504). Thewireless device may send (e.g., transmit) to a base station at least oneuplink DM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at leastone uplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. The base station may configure thewireless device with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to send (e.g., transmit) at one or more symbols of a PUSCHand/or PUCCH. The base station may semi-statically configure thewireless device with a maximum number of front-loaded DM-RS symbols forPUSCH and/or PUCCH. The wireless device may schedule a single-symbolDM-RS and/or double symbol DM-RS based on a maximum number offront-loaded DM-RS symbols, wherein the base station may configure thewireless device with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, for example, at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

Whether or not an uplink PT-RS 507 is present may depend on an RRCconfiguration. A presence of the uplink PT-RS may be wirelessdevice-specifically configured. A presence and/or a pattern of theuplink PT-RS 507 in a scheduled resource may be wirelessdevice-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters used for other purposes (e.g.,Modulation and Coding Scheme (MCS)) which may be indicated by DCI. Ifconfigured, a dynamic presence of uplink PT-RS 507 may be associatedwith one or more DCI parameters comprising at least a MCS. A radionetwork may support a plurality of uplink PT-RS densities defined intime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may determine (e.g., assume) a same precoding for a DMRSport and a PT-RS port. A number of PT-RS ports may be less than a numberof DM-RS ports in a scheduled resource. The uplink PT-RS 507 may beconfined in the scheduled time/frequency duration for a wireless device.

A wireless device may send (e.g., transmit) an SRS 508 to a base stationfor channel state estimation, for example, to support uplink channeldependent scheduling and/or link adaptation. The SRS 508 sent (e.g.,transmitted) by the wireless device may allow for the base station toestimate an uplink channel state at one or more different frequencies. Abase station scheduler may use an uplink channel state to assign one ormore resource blocks of a certain quality (e.g., above a qualitythreshold) for an uplink PUSCH transmission from the wireless device.The base station may semi-statically configure the wireless device withone or more SRS resource sets. For an SRS resource set, the base stationmay configure the wireless device with one or more SRS resources. An SRSresource set applicability may be configured by a higher layer (e.g.,RRC) parameter. An SRS resource in each of one or more SRS resource setsmay be sent (e.g., transmitted) at a time instant, for example, if ahigher layer parameter indicates beam management. The wireless devicemay send (e.g., transmit) one or more SRS resources in different SRSresource sets simultaneously. A new radio network may support aperiodic,periodic, and/or semi-persistent SRS transmissions. The wireless devicemay send (e.g., transmit) SRS resources, for example, based on one ormore trigger types. The one or more trigger types may comprise higherlayer signaling (e.g., RRC) and/or one or more DCI formats (e.g., atleast one DCI format may be used for a wireless device to select atleast one of one or more configured SRS resource sets). An SRS triggertype 0 may refer to an SRS triggered based on a higher layer signaling.An SRS trigger type 1 may refer to an SRS triggered based on one or moreDCI formats. The wireless device may be configured to send (e.g.,transmit) the SRS 508 after a transmission of PUSCH 503 andcorresponding uplink DM-RS 506, for example, if PUSCH 503 and the SRS508 are transmitted in a same slot.

A base station may semi-statically configure a wireless device with oneor more SRS configuration parameters indicating at least one offollowing: an SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, an SRS bandwidth,a frequency hopping bandwidth, a cyclic shift, and/or an SRS sequenceID.

FIG. 5B shows an example downlink channel mapping and downlink physicalsignals. Downlink transport channels may comprise a Downlink-SharedCHannel (DL-SCH) 511, a Paging CHannel (PCH) 512, and/or a BroadcastCHannel (BCH) 513. A transport channel may be mapped to one or morecorresponding physical channels. A UL-SCH 501 may be mapped to aPhysical Uplink Shared CHannel (PUSCH) 503. A RACH 502 may be mapped toa PRACH 505. A DL-SCH 511 and a PCH 512 may be mapped to a PhysicalDownlink Shared CHannel (PDSCH) 514. A BCH 513 may be mapped to aPhysical Broadcast CHannel (PBCH) 516.

A radio network may comprise one or more downlink and/or uplinktransport channels. The radio network may comprise one or more physicalchannels without a corresponding transport channel. The one or morephysical channels may be used for an Uplink Control Information (UCI)509 and/or a Downlink Control Information (DCI) 517. A Physical UplinkControl CHannel (PUCCH) 504 may carry UCI 509 from a wireless device toa base station. A Physical Downlink Control CHannel (PDCCH) 515 maycarry the DCI 517 from a base station to a wireless device. The radionetwork (e.g., NR) may support the UCI 509 multiplexing in the PUSCH503, for example, if the UCI 509 and the PUSCH 503 transmissions maycoincide in a slot (e.g., at least in part). The UCI 509 may comprise atleast one of a CSI, an Acknowledgement (ACK)/Negative Acknowledgement(NACK), and/or a scheduling request. The DCI 517 via the PDCCH 515 mayindicate at least one of following: one or more downlink assignmentsand/or one or more uplink scheduling grants.

In uplink, a wireless device may send (e.g., transmit) one or moreReference Signals (RSs) to a base station. The one or more RSs maycomprise at least one of a Demodulation-RS (DM-RS) 506, a PhaseTracking-RS (PT-RS) 507, and/or a Sounding RS (SRS) 508. In downlink, abase station may send (e.g., transmit, unicast, multicast, and/orbroadcast) one or more RSs to a wireless device. The one or more RSs maycomprise at least one of a Primary Synchronization Signal(PSS)/Secondary Synchronization Signal (SSS) 521, a CSI-RS 522, a DM-RS523, and/or a PT-RS 524.

In a time domain, an SS/PBCH block may comprise one or more OFDM symbols(e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) withinthe SS/PBCH block. An SS/PBCH block may comprise the PSS/SSS 521 and/orthe PBCH 516. In the frequency domain, an SS/PBCH block may comprise oneor more contiguous subcarriers (e.g., 240 contiguous subcarriers withthe subcarriers numbered in increasing order from 0 to 239) within theSS/PBCH block. The PSS/SSS 521 may occupy, for example, 1 OFDM symboland 127 subcarriers. The PBCH 516 may span across, for example, 3 OFDMsymbols and 240 subcarriers. A wireless device may determine (e.g.,assume) that one or more SS/PBCH blocks transmitted with a same blockindex may be quasi co-located, for example, with respect to Dopplerspread, Doppler shift, average gain, average delay, and/or spatial Rxparameters. A wireless device may not determine (e.g., assume) quasico-location for other SS/PBCH block transmissions. A periodicity of anSS/PBCH block may be configured by a radio network (e.g., by an RRCsignaling). One or more time locations in which the SS/PBCH block may besent may be determined by sub-carrier spacing. A wireless device maydetermine (e.g., assume) a band-specific sub-carrier spacing for anSS/PBCH block, for example, unless a radio network has configured thewireless device to determine (e.g., assume) a different sub-carrierspacing.

The downlink CSI-RS 522 may be used for a wireless device to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of the downlink CSI-RS522. A base station may semi-statically configure and/or reconfigure awireless device with periodic transmission of the downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated and/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation of aCSI-RS resource may be triggered dynamically. A CSI-RS configuration maycomprise one or more parameters indicating at least a number of antennaports. A base station may configure a wireless device with 32 ports, orany other number of ports. A base station may semi-statically configurea wireless device with one or more CSI-RS resource sets. One or moreCSI-RS resources may be allocated from one or more CSI-RS resource setsto one or more wireless devices. A base station may semi-staticallyconfigure one or more parameters indicating CSI RS resource mapping, forexample, time-domain location of one or more CSI-RS resources, abandwidth of a CSI-RS resource, and/or a periodicity. A wireless devicemay be configured to use the same OFDM symbols for the downlink CSI-RS522 and the Control Resource Set (CORESET), for example, if the downlinkCSI-RS 522 and the CORESET are spatially quasi co-located and resourceelements associated with the downlink CSI-RS 522 are the outside of PRBsconfigured for the CORESET. A wireless device may be configured to usethe same OFDM symbols for downlink CSI-RS 522 and SS/PBCH blocks, forexample, if the downlink CSI-RS 522 and SS/PBCH blocks are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are outside of the PRBs configured for the SS/PBCH blocks.

A wireless device may send (e.g., transmit) one or more downlink DM-RSs523 to a base station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). A radio network may support one or more variable and/orconfigurable DM-RS patterns for data demodulation. At least one downlinkDM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-staticallyconfigure a wireless device with a maximum number of front-loaded DM-RSsymbols for PDSCH 514. A DM-RS configuration may support one or moreDM-RS ports. A DM-RS configuration may support at least 8 orthogonaldownlink DM-RS ports, for example, for single user-MIMO. ADM-RSconfiguration may support 12 orthogonal downlink DM-RS ports, forexample, for multiuser-MIMO. A radio network may support, for example,at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein aDM-RS location, DM-RS pattern, and/or scrambling sequence may be thesame or different.

Whether or not the downlink PT-RS 524 is present may depend on an RRCconfiguration. A presence of the downlink PT-RS 524 may be wirelessdevice-specifically configured. A presence and/or a pattern of thedownlink PT-RS 524 in a scheduled resource may be wirelessdevice-specifically configured, for example, by a combination of RRCsignaling and/or an association with one or more parameters used forother purposes (e.g., MCS) which may be indicated by the DCI. Ifconfigured, a dynamic presence of the downlink PT-RS 524 may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of PT-RS densities in atime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may determine (e.g., assume) the same precoding for aDMRS port and a PT-RS port. A number of PT-RS ports may be less than anumber of DM-RS ports in a scheduled resource. The downlink PT-RS 524may be confined in the scheduled time/frequency duration for a wirelessdevice.

FIG. 6 shows an example transmission time and reception time, as well asan example frame structure, for a carrier. A multicarrier OFDMcommunication system may include one or more carriers, for example,ranging from 1 to 32 carriers (such as for carrier aggregation) orranging from 1 to 64 carriers (such as for dual connectivity). Differentradio frame structures may be supported (e.g., for FDD and/or for TDDduplex mechanisms). FIG. 6 shows an example frame timing. Downlink anduplink transmissions may be organized into radio frames 601. Radio frameduration may be 10 milliseconds (ms). A 10 ms radio frame 601 may bedivided into ten equally sized subframes 602, each with a 1 ms duration.Subframe(s) may comprise one or more slots (e.g., slots 603 and 605)depending on subcarrier spacing and/or CP length. For example, asubframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz and 480 kHzsubcarrier spacing may comprise one, two, four, eight, sixteen andthirty-two slots, respectively. In FIG. 6, a subframe may be dividedinto two equally sized slots 603 with 0.5 ms duration. For example, 10subframes may be available for downlink transmission and 10 subframesmay be available for uplink transmissions in a 10 ms interval. Othersubframe durations such as, for example, 0.5 ms, 1 ms, 2 ms, and 5 msmay be supported. Uplink and downlink transmissions may be separated inthe frequency domain. Slot(s) may include a plurality of OFDM symbols604. The number of OFDM symbols 604 in a slot 605 may depend on thecyclic prefix length. A slot may be 14 OFDM symbols for the samesubcarrier spacing of up to 480 kHz with normal CP. A slot may be 12OFDM symbols for the same subcarrier spacing of 60 kHz with extended CP.A slot may comprise downlink, uplink, and/or a downlink part and anuplink part, and/or alike.

FIG. 7A shows example sets of OFDM subcarriers. A base station maycommunicate with a wireless device using a carrier having an examplechannel bandwidth 700. Arrow(s) in the example may depict a subcarrierin a multicarrier OFDM system. The OFDM system may use technology suchas OFDM technology, SC-FDMA technology, and/or the like. An arrow 701shows a subcarrier transmitting information symbols. A subcarrierspacing 702, between two contiguous subcarriers in a carrier, may be anyone of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, or any other frequency.Different subcarrier spacing may correspond to different transmissionnumerologies. A transmission numerology may comprise at least: anumerology index; a value of subcarrier spacing; and/or a type of cyclicprefix (CP). A base station may send (e.g., transmit) to and/or receivefrom a wireless device via a number of subcarriers 703 in a carrier. Abandwidth occupied by a number of subcarriers 703 (e.g., transmissionbandwidth) may be smaller than the channel bandwidth 700 of a carrier,for example, due to guard bands 704 and 705. Guard bands 704 and 705 maybe used to reduce interference to and from one or more neighborcarriers. A number of subcarriers (e.g., transmission bandwidth) in acarrier may depend on the channel bandwidth of the carrier and/or thesubcarrier spacing. A transmission bandwidth, for a carrier with a 20MHz channel bandwidth and a 15 kHz subcarrier spacing, may be in numberof 1024 subcarriers.

A base station and a wireless device may communicate with multiplecomponent carriers (CCs), for example, if configured with CA. Differentcomponent carriers may have different bandwidth and/or differentsubcarrier spacing, for example, if CA is supported. A base station maysend (e.g., transmit) a first type of service to a wireless device via afirst component carrier. The base station may send (e.g., transmit) asecond type of service to the wireless device via a second componentcarrier. Different types of services may have different servicerequirements (e.g., data rate, latency, reliability), which may besuitable for transmission via different component carriers havingdifferent subcarrier spacing and/or different bandwidth.

FIG. 7B shows examples of component carriers. A first component carriermay comprise a first number of subcarriers 706 having a first subcarrierspacing 709. A second component carrier may comprise a second number ofsubcarriers 707 having a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 havinga third subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 shows an example of OFDM radio resources. A carrier may have atransmission bandwidth 801. A resource grid may be in a structure offrequency domain 802 and time domain 803. A resource grid may comprise afirst number of OFDM symbols in a subframe and a second number ofresource blocks, starting from a common resource block indicated byhigher-layer signaling (e.g., RRC signaling), for a transmissionnumerology and a carrier. In a resource grid, a resource element 805 maycomprise a resource unit that may be identified and/or indicated by asubcarrier index and a symbol index. A subframe may comprise a firstnumber of OFDM symbols 807 that may depend on a numerology associatedwith a carrier. A subframe may have 14 OFDM symbols for a carrier, forexample, if a subcarrier spacing of a numerology of a carrier is 15 kHz.A subframe may have 28 OFDM symbols, for example, if a subcarrierspacing of a numerology is 30 kHz. A subframe may have 56 OFDM symbols,for example, if a subcarrier spacing of a numerology is 60 kHz. Asubcarrier spacing of a numerology may comprise any other frequency. Asecond number of resource blocks comprised in a resource grid of acarrier may depend on a bandwidth and a numerology of the carrier.

A resource block 806 may comprise 12 subcarriers. Multiple resourceblocks may be grouped into a Resource Block Group (RBG) 804. A size of aRBG may depend on at least one of: a RRC message indicating a RBG sizeconfiguration; a size of a carrier bandwidth; and/or a size of abandwidth part of a carrier. A carrier may comprise multiple bandwidthparts. A first bandwidth part of a carrier may have a differentfrequency location and/or a different bandwidth from a second bandwidthpart of the carrier.

A base station may send (e.g., transmit), to a wireless device, adownlink control information comprising a downlink or uplink resourceblock assignment. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets (e.g., transport blocks).The data packets may be scheduled on and transmitted via one or moreresource blocks and one or more slots indicated by parameters indownlink control information and/or RRC message(s). A starting symbolrelative to a first slot of the one or more slots may be indicated tothe wireless device. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets. The data packets may bescheduled for transmission on one or more RBGs and in one or more slots.

A base station may send (e.g., transmit), to a wireless device, downlinkcontrol information comprising a downlink assignment. The base stationmay send (e.g., transmit) the DCI via one or more PDCCHs. The downlinkassignment may comprise parameters indicating at least one of amodulation and coding format; resource allocation; and/or HARQinformation related to the DL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. A basestation may allocate (e.g., dynamically) resources to a wireless device,for example, via a Cell-Radio Network Temporary Identifier (C-RNTI) onone or more PDCCHs. The wireless device may monitor the one or morePDCCHs, for example, in order to find possible allocation if itsdownlink reception is enabled. The wireless device may receive one ormore downlink data packets on one or more PDSCH scheduled by the one ormore PDCCHs, for example, if the wireless device successfully detectsthe one or more PDCCHs.

A base station may allocate Configured Scheduling (CS) resources fordown link transmission to a wireless device. The base station may send(e.g., transmit) one or more RRC messages indicating a periodicity ofthe CS grant. The base station may send (e.g., transmit) DCI via a PDCCHmessage addressed to a Configured Scheduling-RNTI (CS-RNTI) activatingthe CS resources. The DCI may comprise parameters indicating that thedownlink grant is a CS grant. The CS grant may be implicitly reusedaccording to the periodicity defined by the one or more RRC messages.The CS grant may be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit), to a wireless device via oneor more PDCCH messages, downlink control information comprising anuplink grant. The uplink grant may comprise parameters indicating atleast one of a modulation and coding format; a resource allocation;and/or HARQ information related to the UL-SCH. The resource allocationmay comprise parameters of resource block allocation; and/or slotallocation. The base station may dynamically allocate resources to thewireless device via a C-RNTI on one or more PDCCH messages. The wirelessdevice may monitor the one or more PDCCH messages, for example, in orderto find possible resource allocation. The wireless device may send(e.g., transmit) one or more uplink data packets via one or more PUSCHscheduled by the one or more PDCCH messages, for example, if thewireless device successfully detects the one or more PDCCH messages.

The base station may allocate CS resources for uplink data transmissionto a wireless device. The base station may transmit one or more RRCmessages indicating a periodicity of the CS grant. The base station maysend (e.g., transmit) DCI via a PDCCH message addressed to a CS-RNTI toactivate the CS resources. The DCI may comprise parameters indicatingthat the uplink grant is a CS grant. The CS grant may be implicitlyreused according to the periodicity defined by the one or more RRCmessage, The CS grant may be implicitly reused, for example, untildeactivated.

A base station may send (e.g., transmit) DCI and/or control signalingvia a PDCCH message. The DCI may comprise a format of a plurality offormats. The DCI may comprise downlink and/or uplink schedulinginformation (e.g., resource allocation information, HARQ relatedparameters, MCS), request(s) for CSI (e.g., aperiodic CQI reports),request(s) for an SRS, uplink power control commands for one or morecells, one or more timing information (e.g., TB transmission/receptiontiming, HARQ feedback timing, etc.), and/or the like. The DCI mayindicate an uplink grant comprising transmission parameters for one ormore transport blocks. The DCI may indicate a downlink assignmentindicating parameters for receiving one or more transport blocks. TheDCI may be used by the base station to initiate a contention-free randomaccess at the wireless device. The base station may send (e.g.,transmit) DCI comprising a slot format indicator (SFI) indicating a slotformat. The base station may send (e.g., transmit) DCI comprising apreemption indication indicating the PRB(s) and/or OFDM symbol(s) inwhich a wireless device may determine (e.g., assume) no transmission isintended for the wireless device. The base station may send (e.g.,transmit) DCI for group power control of the PUCCH, the PUSCH, and/or anSRS. DCI may correspond to an RNTI. The wireless device may obtain anRNTI after or in response to completing the initial access (e.g.,C-RNTI). The base station may configure an RNTI for the wireless (e.g.,CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI,etc.). The wireless device may determine (e.g., compute) an RNTI (e.g.,the wireless device may determine the RA-RNTI based on resources usedfor transmission of a preamble). An RNTI may have a pre-configured value(e.g., P-RNTI or SI-RNTI). The wireless device may monitor a groupcommon search space which may be used by the base station for sending(e.g., transmitting) DCIs that are intended for a group of wirelessdevices. A group common DCI may correspond to an RNTI which is commonlyconfigured for a group of wireless devices. The wireless device maymonitor a wireless device-specific search space. A wireless devicespecific DCI may correspond to an RNTI configured for the wirelessdevice.

A communications system (e.g., an NR system) may support a single beamoperation and/or a multi-beam operation. In a multi-beam operation, abase station may perform a downlink beam sweeping to provide coveragefor common control channels and/or downlink SS blocks, which maycomprise at least a PSS, a SSS, and/or PBCH. A wireless device maymeasure quality of a beam pair link using one or more RSs. One or moreSS blocks, or one or more CSI-RS resources (e.g., which may beassociated with a CSI-RS resource index (CRI)), and/or one or moreDM-RSs of a PBCH, may be used as an RS for measuring a quality of a beampair link. The quality of a beam pair link may be based on a referencesignal received power (RSRP) value, a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. An RS resource and DM-RSs of a control channel may be calledQCLed, for example, if channel characteristics from a transmission on anRS to a wireless device, and that from a transmission on a controlchannel to a wireless device, are similar or the same under a configuredcriterion. In a multi-beam operation, a wireless device may perform anuplink beam sweeping to access a cell.

A wireless device may be configured to monitor a PDCCH on one or morebeam pair links simultaneously, for example, depending on a capabilityof the wireless device. This monitoring may increase robustness againstbeam pair link blocking. A base station may send (e.g., transmit) one ormore messages to configure the wireless device to monitor the PDCCH onone or more beam pair links in different PDCCH OFDM symbols. A basestation may send (e.g., transmit) higher layer signaling (e.g., RRCsignaling) and/or a MAC CE comprising parameters related to the Rx beamsetting of the wireless device for monitoring the PDCCH on one or morebeam pair links. The base station may send (e.g., transmit) anindication of a spatial QCL assumption between an DL RS antenna port(s)(e.g., a cell-specific CSI-RS, a wireless device-specific CSI-RS, an SSblock, and/or a PBCH with or without DM-RSs of the PBCH) and/or DL RSantenna port(s) for demodulation of a DL control channel. Signaling forbeam indication for a PDCCH may comprise MAC CE signaling, RRCsignaling, DCI signaling, and/or specification-transparent and/orimplicit method, and/or any combination of signaling methods.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of a DL data channel, for example, forreception of a unicast DL data channel. The base station may send (e.g.,transmit) DCI (e.g., downlink grants) comprising information indicatingthe RS antenna port(s). The information may indicate RS antenna port(s)that may be QCL-ed with the DM-RS antenna port(s). A different set ofDM-RS antenna port(s) for a DL data channel may be indicated as QCL witha different set of the RS antenna port(s).

FIG. 9A shows an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may determine(e.g., assume) that SS blocks form an SS burst 940, and an SS burst set950. The SS burst set 950 may have a given periodicity. A base station120 may send (e.g., transmit) SS blocks in multiple beams, togetherforming a SS burst 940, for example, in a multi-beam operation. One ormore SS blocks may be sent (e.g., transmitted) on one beam. If multipleSS bursts 940 are transmitted with multiple beams, SS bursts togethermay form SS burst set 950.

A wireless device may use CSI-RS for estimating a beam quality of a linkbetween a wireless device and a base station, for example, in the multibeam operation. A beam may be associated with a CSI-RS. A wirelessdevice may (e.g., based on a RSRP measurement on CSI-RS) report a beamindex, which may be indicated in a CRI for downlink beam selectionand/or associated with an RSRP value of a beam. A CSI-RS may be sent(e.g., transmitted) on a CSI-RS resource, which may comprise at leastone of: one or more antenna ports and/or one or more time and/orfrequency radio resources. A CSI-RS resource may be configured in acell-specific way such as by common RRC signaling, or in a wirelessdevice-specific way such as by dedicated RRC signaling and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be sent (e.g., transmitted) periodically, usingaperiodic transmission, or using a multi-shot or semi-persistenttransmission. In a periodic transmission in FIG. 9A, a base station 120may send (e.g., transmit) configured CSI-RS resources 940 periodicallyusing a configured periodicity in a time domain. In an aperiodictransmission, a configured CSI-RS resource may be sent (e.g.,transmitted) in a dedicated time slot. In a multi-shot and/orsemi-persistent transmission, a configured CSI-RS resource may be sent(e.g., transmitted) within a configured period. Beams used for CSI-RStransmission may have a different beam width than beams used forSS-blocks transmission.

FIG. 9B shows an example of a beam management procedure, such as in anexample new radio network. The base station 120 and/or the wirelessdevice 110 may perform a downlink L1/L2 beam management procedure. Oneor more of the following downlink L1/L2 beam management procedures maybe performed within one or more wireless devices 110 and one or morebase stations 120. A P1 procedure 910 may be used to enable the wirelessdevice 110 to measure one or more Transmission (Tx) beams associatedwith the base station 120, for example, to support a selection of afirst set of Tx beams associated with the base station 120 and a firstset of Rx beam(s) associated with the wireless device 110. A basestation 120 may sweep a set of different Tx beams, for example, forbeamforming at a base station 120 (such as shown in the top row, in acounter-clockwise direction). A wireless device 110 may sweep a set ofdifferent Rx beams, for example, for beamforming at a wireless device110 (such as shown in the bottom row, in a clockwise direction). A P2procedure 920 may be used to enable a wireless device 110 to measure oneor more Tx beams associated with a base station 120, for example, topossibly change a first set of Tx beams associated with a base station120. A P2 procedure 920 may be performed on a possibly smaller set ofbeams (e.g., for beam refinement) than in the P1 procedure 910. A P2procedure 920 may be a special example of a P1 procedure 910. A P3procedure 930 may be used to enable a wireless device 110 to measure atleast one Tx beam associated with a base station 120, for example, tochange a first set of Rx beams associated with a wireless device 110.

A wireless device 110 may send (e.g., transmit) one or more beammanagement reports to a base station 120. In one or more beam managementreports, a wireless device 110 may indicate one or more beam pairquality parameters comprising one or more of: a beam identification; anRSRP; a Precoding Matrix Indicator (PMI), Channel Quality Indicator(CQI), and/or Rank Indicator (RI) of a subset of configured beams. Basedon one or more beam management reports, the base station 120 may send(e.g., transmit) to a wireless device 110 a signal indicating that oneor more beam pair links are one or more serving beams. The base station120 may send (e.g., transmit) the PDCCH message and the PDSCH for awireless device 110 using one or more serving beams.

A communications network (e.g., a new radio network) may support aBandwidth Adaptation (BA). Receive and/or transmit bandwidths that maybe configured for a wireless device using a BA may not be large. Receiveand/or transmit bandwidth may not be as large as a bandwidth of a cell.Receive and/or transmit bandwidths may be adjustable. A wireless devicemay change receive and/or transmit bandwidths, for example, to reduce(e.g., shrink) the bandwidth(s) at (e.g., during) a period of lowactivity such as to save power. A wireless device may change a locationof receive and/or transmit bandwidths in a frequency domain, forexample, to increase scheduling flexibility. A wireless device maychange a subcarrier spacing, for example, to allow different services.

A Bandwidth Part (BWP) may comprise a subset of a total cell bandwidthof a cell. A base station may configure a wireless device with one ormore BWPs, for example, to achieve a BA. A base station may indicate, toa wireless device, which of the one or more (configured) BWPs is anactive BWP.

FIG. 10 shows an example of BWP configurations. BWPs may be configuredas follows: BWP1 (1010 and 1050) with a width of 40 MHz and subcarrierspacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz andsubcarrier spacing of 15 kHz; BWP3 1030 with a width of 20 MHz andsubcarrier spacing of 60 kHz. Any number of BWP configurations maycomprise any other width and subcarrier spacing combination.

A wireless device, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g., RRC layer).The wireless device may be configured for a cell with: a set of one ormore BWPs (e.g., at most four BWPs) for reception (e.g., a DL BWP set)in a DL bandwidth by at least one parameter DL-BWP; and a set of one ormore BWPs (e.g., at most four BWPs) for transmissions (e.g., UL BWP set)in an UL bandwidth by at least one parameter UL-BWP.

A base station may configure a wireless device with one or more UL andDL BWP pairs, for example, to enable BA on the PCell. To enable BA onSCells (e.g., for CA), a base station may configure a wireless device atleast with one or more DL BWPs (e.g., there may be none in an UL).

An initial active DL BWP may comprise at least one of a location andnumber of contiguous PRBs, a subcarrier spacing, or a cyclic prefix, forexample, for a CORESETs for at least one common search space. Foroperation on the PCell, one or more higher layer parameters may indicateat least one initial UL BWP for a random access procedure. If a wirelessdevice is configured with a secondary carrier on a primary cell, thewireless device may be configured with an initial BWP for random accessprocedure on a secondary carrier.

A wireless device may expect that a center frequency for a DL BWP may besame as a center frequency for a UL BWP, for example, for unpairedspectrum operation. A base station may semi-statically configure awireless device for a cell with one or more parameters, for example, fora DL BWP or an UL BWP in a set of one or more DL BWPs or one or more ULBWPs, respectively. The one or more parameters may indicate one or moreof following: a subcarrier spacing; a cyclic prefix; a number ofcontiguous PRBs; an index in the set of one or more DL BWPs and/or oneor more UL BWPs; a link between a DL BWP and an UL BWP from a set ofconfigured DL BWPs and UL BWPs; a DCI detection to a PDSCH receptiontiming; a PDSCH reception to a HARQ-ACK transmission timing value; a DCIdetection to a PUSCH transmission timing value; and/or an offset of afirst PRB of a DL bandwidth or an UL bandwidth, respectively, relativeto a first PRB of a bandwidth.

For a DL BWP in a set of one or more DL BWPs on a PCell, a base stationmay configure a wireless device with one or more control resource setsfor at least one type of common search space and/or one wirelessdevice-specific search space. A base station may not configure awireless device without a common search space on a PCell, or on aPSCell, in an active DL BWP. For an UL BWP in a set of one or more ULBWPs, a base station may configure a wireless device with one or moreresource sets for one or more PUCCH transmissions.

DCI may comprise a BWP indicator field. The BWP indicator field valuemay indicate an active DL BWP, from a configured DL BWP set, for one ormore DL receptions. The BWP indicator field value may indicate an activeUL BWP, from a configured UL BWP set, for one or more UL transmissions.

For a PCell, a base station may semi-statically configure a wirelessdevice with a default DL BWP among configured DL BWPs. If a wirelessdevice is not provided a default DL BWP, a default BWP may be an initialactive DL BWP.

A base station may configure a wireless device with a timer value for aPCell. A wireless device may start a timer (e.g., a BWP inactivitytimer), for example, if a wireless device detects DCI indicating anactive DL BWP, other than a default DL BWP, for a paired spectrumoperation, and/or if a wireless device detects DCI indicating an activeDL BWP or UL BWP, other than a default DL BWP or UL BWP, for an unpairedspectrum operation. The wireless device may increment the timer by aninterval of a first value (e.g., the first value may be 1 millisecond,0.5 milliseconds, or any other time duration), for example, if thewireless device does not detect DCI at (e.g., during) the interval for apaired spectrum operation or for an unpaired spectrum operation. Thetimer may expire at a time that the timer is equal to the timer value. Awireless device may switch to the default DL BWP from an active DL BWP,for example, if the timer expires.

A base station may semi-statically configure a wireless device with oneor more BWPs. A wireless device may switch an active BWP from a firstBWP to a second BWP, for example, after or in response to receiving DCIindicating the second BWP as an active BWP, and/or after or in responseto an expiry of BWP inactivity timer (e.g., the second BWP may be adefault BWP). FIG. 10 shows an example of three BWPs configured, BWP1(1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and1040) may be a default BWP. BWP1 (1010) may be an initial active BWP. Awireless device may switch an active BWP from BWP1 1010 to BWP2 1020,for example, after or in response to an expiry of the BWP inactivitytimer. A wireless device may switch an active BWP from BWP2 1020 to BWP31030, for example, after or in response to receiving DCI indicating BWP31030 as an active BWP. Switching an active BWP from BWP3 1030 to BWP21040 and/or from BWP2 1040 to BWP1 1050 may be after or in response toreceiving DCI indicating an active BWP, and/or after or in response toan expiry of BWP inactivity timer.

Wireless device procedures on a secondary cell may be same as on aprimary cell using the timer value for the secondary cell and thedefault DL BWP for the secondary cell, for example, if a wireless deviceis configured for a secondary cell with a default DL BWP amongconfigured DL BWPs and a timer value. A wireless device may use anindicated DL BWP and an indicated UL BWP on a secondary cell as arespective first active DL BWP and first active UL BWP on a secondarycell or carrier, for example, if a base station configures a wirelessdevice with a first active DL BWP and a first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows using a multi connectivity(e.g., dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A shows an example of a protocol structure of awireless device 110 (e.g., UE) with CA and/or multi connectivity. FIG.11B shows an example of a protocol structure of multiple base stationswith CA and/or multi connectivity. The multiple base stations maycomprise a master node, MN 1130 (e.g., a master node, a master basestation, a master gNB, a master eNB, and/or the like) and a secondarynode, SN 1150 (e.g., a secondary node, a secondary base station, asecondary gNB, a secondary eNB, and/or the like). A master node 1130 anda secondary node 1150 may co-work to communicate with a wireless device110.

If multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception and/ortransmission functions in an RRC connected state, may be configured toutilize radio resources provided by multiple schedulers of a multiplebase stations. Multiple base stations may be inter-connected via anon-ideal or ideal backhaul (e.g., Xn interface, X2 interface, and/orthe like). A base station involved in multi connectivity for a certainwireless device may perform at least one of two different roles: a basestation may act as a master base station or act as a secondary basestation. In multi connectivity, a wireless device may be connected toone master base station and one or more secondary base stations. Amaster base station (e.g., the MN 1130) may provide a master cell group(MCG) comprising a primary cell and/or one or more secondary cells for awireless device (e.g., the wireless device 110). A secondary basestation (e.g., the SN 1150) may provide a secondary cell group (SCG)comprising a primary secondary cell (PSCell) and/or one or moresecondary cells for a wireless device (e.g., the wireless device 110).

In multi connectivity, a radio protocol architecture that a bearer usesmay depend on how a bearer is setup. Three different types of bearersetup options may be supported: an MCG bearer, an SCG bearer, and/or asplit bearer. A wireless device may receive and/or send (e.g., transmit)packets of an MCG bearer via one or more cells of the MCG. A wirelessdevice may receive and/or send (e.g., transmit) packets of an SCG bearervia one or more cells of an SCG. Multi-connectivity may indicate havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not be configuredand/or implemented.

A wireless device (e.g., wireless device 110) may send (e.g., transmit)and/or receive: packets of an MCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC1114), and a MAC layer (e.g., MN MAC 1118); packets of a split bearervia an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112),one of a master or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116),and one of a master or secondary MAC layer (e.g., MN MAC 1118, SN MAC1119); and/or packets of an SCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC1117), and a MAC layer (e.g., MN MAC 1119).

A master base station (e.g., MN 1130) and/or a secondary base station(e.g., SN 1150) may send (e.g., transmit) and/or receive: packets of anMCG bearer via a master or secondary node SDAP layer (e.g., SDAP 1120,SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1121,NR PDCP 1142), a master node RLC layer (e.g., MN RLC 1124, MN RLC 1125),and a master node MAC layer (e.g., MN MAC 1128); packets of an SCGbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1122, NRPDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147),and a secondary node MAC layer (e.g., SN MAC 1148); packets of a splitbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1123, NRPDCP 1141), a master or secondary node RLC layer (e.g., MN RLC 1126, SNRLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAClayer (e.g., MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities, such as one MAC entity (e.g., MN MAC 1118) for a master basestation, and other MAC entities (e.g., SN MAC 1119) for a secondary basestation. In multi-connectivity, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and SCGs comprising serving cells of asecondary base station. For an SCG, one or more of followingconfigurations may be used. At least one cell of an SCG may have aconfigured UL CC and at least one cell of a SCG, named as primarysecondary cell (e.g., PSCell, PCell of SCG, PCell), and may beconfigured with PUCCH resources. If an SCG is configured, there may beat least one SCG bearer or one split bearer. After or upon detection ofa physical layer problem or a random access problem on a PSCell, or anumber of NR RLC retransmissions has been reached associated with theSCG, or after or upon detection of an access problem on a PSCellassociated with (e.g., during) a SCG addition or an SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, a DLdata transfer over a master base station may be maintained (e.g., for asplit bearer). An NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer. A PCell and/or a PSCell may not be de-activated. APSCell may be changed with a SCG change procedure (e.g., with securitykey change and a RACH procedure). A bearer type change between a splitbearer and a SCG bearer, and/or simultaneous configuration of a SCG anda split bearer, may or may not be supported.

With respect to interactions between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be used. A master base station and/or a secondary basestation may maintain RRM measurement configurations of a wirelessdevice. A master base station may determine (e.g., based on receivedmeasurement reports, traffic conditions, and/or bearer types) to requesta secondary base station to provide additional resources (e.g., servingcells) for a wireless device. After or upon receiving a request from amaster base station, a secondary base station may create and/or modify acontainer that may result in a configuration of additional serving cellsfor a wireless device (or decide that the secondary base station has noresource available to do so). For a wireless device capabilitycoordination, a master base station may provide (e.g., all or a part of)an AS configuration and wireless device capabilities to a secondary basestation. A master base station and a secondary base station may exchangeinformation about a wireless device configuration such as by using RRCcontainers (e.g., inter-node messages) carried via Xn messages. Asecondary base station may initiate a reconfiguration of the secondarybase station existing serving cells (e.g., PUCCH towards the secondarybase station). A secondary base station may decide which cell is aPSCell within a SCG. A master base station may or may not change contentof RRC configurations provided by a secondary base station. A masterbase station may provide recent (and/or the latest) measurement resultsfor SCG cell(s), for example, if an SCG addition and/or an SCG SCelladdition occurs. A master base station and secondary base stations mayreceive information of SFN and/or subframe offset of each other from anOAM and/or via an Xn interface (e.g., for a purpose of DRX alignmentand/or identification of a measurement gap). Dedicated RRC signaling maybe used for sending required system information of a cell as for CA, forexample, if adding a new SCG SCell, except for an SFN acquired from anMIB of a PSCell of a SCG.

FIG. 12 shows an example of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival in (e.g., during) a state of RRC_CONNECTED (e.g., if ULsynchronization status is non-synchronized), transition fromRRC_Inactive, and/or request for other system information. A PDCCHorder, a wireless device (e.g., a MAC entity of the wireless device),and/or a beam failure indication may initiate a random access procedure.

A random access procedure may comprise or be one of at least acontention based random access procedure and/or a contention free randomaccess procedure. A contention based random access procedure maycomprise one or more Msg 1 1220 transmissions, one or more Msg2 1230transmissions, one or more Msg3 1240 transmissions, and contentionresolution 1250. A contention free random access procedure may compriseone or more Msg 1 1220 transmissions and one or more Msg2 1230transmissions. One or more of Msg 1 1220, Msg 2 1230, Msg 3 1240, and/orcontention resolution 1250 may be transmitted in the same step. Atwo-step random access procedure, for example, may comprise a firsttransmission (e.g., Msg A) and a second transmission (e.g., Msg B). Thefirst transmission (e.g., Msg A) may comprise transmitting, by awireless device (e.g., wireless device 110) to a base station (e.g.,base station 120), one or more messages indicating an equivalent and/orsimilar contents of Msg1 1220 and Msg3 1240 of a four-step random accessprocedure. The second transmission (e.g., Msg B) may comprisetransmitting, by the base station (e.g., base station 120) to a wirelessdevice (e.g., wireless device 110) after or in response to the firstmessage, one or more messages indicating an equivalent and/or similarcontent of Msg2 1230 and contention resolution 1250 of a four-steprandom access procedure.

A base station may send (e.g., transmit, unicast, multicast, broadcast,etc.), to a wireless device, a RACH configuration 1210 via one or morebeams. The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: an available set of PRACHresources for a transmission of a random access preamble, initialpreamble power (e.g., random access preamble initial received targetpower), an RSRP threshold for a selection of a SS block andcorresponding PRACH resource, a power-ramping factor (e.g., randomaccess preamble power ramping step), a random access preamble index, amaximum number of preamble transmissions, preamble group A and group B,a threshold (e.g., message size) to determine the groups of randomaccess preambles, a set of one or more random access preambles for asystem information request and corresponding PRACH resource(s) (e.g., ifany), a set of one or more random access preambles for a beam failurerecovery request and corresponding PRACH resource(s) (e.g., if any), atime window to monitor RA response(s), a time window to monitorresponse(s) on a beam failure recovery request, and/or a contentionresolution timer.

The Msg1 1220 may comprise one or more transmissions of a random accesspreamble. For a contention based random access procedure, a wirelessdevice may select an SS block with an RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a wireless device may select oneor more random access preambles from a group A or a group B, forexample, depending on a potential Msg3 1240 size. If a random accesspreambles group B does not exist, a wireless device may select the oneor more random access preambles from a group A. A wireless device mayselect a random access preamble index randomly (e.g., with equalprobability or a normal distribution) from one or more random accesspreambles associated with a selected group. If a base stationsemi-statically configures a wireless device with an association betweenrandom access preambles and SS blocks, the wireless device may select arandom access preamble index randomly with equal probability from one ormore random access preambles associated with a selected SS block and aselected group.

A wireless device may initiate a contention free random accessprocedure, for example, based on a beam failure indication from a lowerlayer. A base station may semi-statically configure a wireless devicewith one or more contention free PRACH resources for a beam failurerecovery request associated with at least one of SS blocks and/orCSI-RSs. A wireless device may select a random access preamble indexcorresponding to a selected SS block or a CSI-RS from a set of one ormore random access preambles for a beam failure recovery request, forexample, if at least one of the SS blocks with an RSRP above a firstRSRP threshold amongst associated SS blocks is available, and/or if atleast one of CSI-RSs with a RSRP above a second RSRP threshold amongstassociated CSI-RSs is available.

A wireless device may receive, from a base station, a random accesspreamble index via PDCCH or RRC message for a contention free randomaccess procedure. The wireless device may select a random accesspreamble index, for example, if a base station does not configure awireless device with at least one contention free PRACH resourceassociated with SS blocks or CSI-RS. The wireless device may select theat least one SS block and/or select a random access preamblecorresponding to the at least one SS block, for example, if a basestation configures the wireless device with one or more contention freePRACH resources associated with SS blocks and/or if at least one SSblock with a RSRP above a first RSRP threshold amongst associated SSblocks is available. The wireless device may select the at least oneCSI-RS and/or select a random access preamble corresponding to the atleast one CSI-RS, for example, if a base station configures a wirelessdevice with one or more contention free PRACH resources associated withCSI-RSs and/or if at least one CSI-RS with a RSRP above a second RSPRthreshold amongst the associated CSI-RSs is available.

A wireless device may perform one or more Msg1 1220 transmissions, forexample, by sending (e.g., transmitting) the selected random accesspreamble. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected SS block, for example,if the wireless device selects an SS block and is configured with anassociation between one or more PRACH occasions and/or one or more SSblocks. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected CSI-RS, for example, ifthe wireless device selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs.The wireless device may send (e.g., transmit), to a base station, aselected random access preamble via a selected PRACH occasions. Thewireless device may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. The wireless device may determine anRA-RNTI associated with a selected PRACH occasion in which a selectedrandom access preamble is sent (e.g., transmitted). The wireless devicemay not determine an RA-RNTI for a beam failure recovery request. Thewireless device may determine an RA-RNTI at least based on an index of afirst OFDM symbol, an index of a first slot of a selected PRACHoccasions, and/or an uplink carrier index for a transmission of Msg11220.

A wireless device may receive, from a base station, a random accessresponse, Msg 2 1230.

The wireless device may start a time window (e.g., ra-ResponseWindow) tomonitor a random access response. For a beam failure recovery procedure,the base station may configure the wireless device with a different timewindow (e.g., bfr-ResponseWindow) to monitor response to on a beamfailure recovery request. The wireless device may start a time window(e.g., ra-ResponseWindow or bfr-ResponseWindow) at a start of a firstPDCCH occasion, for example, after a fixed duration of one or moresymbols from an end of a preamble transmission. If the wireless devicesends (e.g., transmits) multiple preambles, the wireless device maystart a time window at a start of a first PDCCH occasion after a fixedduration of one or more symbols from an end of a first preambletransmission. The wireless device may monitor a PDCCH of a cell for atleast one random access response identified and/or indicated by aRA-RNTI, or for at least one response to a beam failure recovery requestidentified and/or indicated by a C-RNTI, at a time that a timer for atime window is running

A wireless device may determine that a reception of random accessresponse is successful, for example, if at least one random accessresponse comprises a random access preamble identifier corresponding toa random access preamble sent (e.g., transmitted) by the wirelessdevice. The wireless device may determine that the contention freerandom access procedure is successfully completed, for example, if areception of a random access response is successful. The wireless devicemay determine that a contention free random access procedure issuccessfully complete, for example, if a contention-free random accessprocedure is triggered for a beam failure recovery request and if aPDCCH transmission is addressed to a C-RNTI. The wireless device maydetermine that the random access procedure is successfully completed,and may indicate a reception of an acknowledgement for a systeminformation request to upper layers, for example, if at least one randomaccess response comprises a random access preamble identifier. Thewireless device may stop sending (e.g., transmitting) remainingpreambles (if any) after or in response to a successful reception of acorresponding random access response, for example, if the wirelessdevice has signaled multiple preamble transmissions.

The wireless device may perform one or more Msg 3 1240 transmissions,for example, after or in response to a successful reception of randomaccess response (e.g., for a contention based random access procedure).The wireless device may adjust an uplink transmission timing, forexample, based on a timing advanced command indicated by a random accessresponse. The wireless device may send (e.g., transmit) one or moretransport blocks, for example, based on an uplink grant indicated by arandom access response. Subcarrier spacing for PUSCH transmission forMsg3 1240 may be provided by at least one higher layer (e.g., RRC)parameter. The wireless device may send (e.g., transmit) a random accesspreamble via a PRACH, and Msg3 1240 via PUSCH, on the same cell. A basestation may indicate an UL BWP for a PUSCH transmission of Msg3 1240 viasystem information block. The wireless device may use HARQ for aretransmission of Msg 3 1240.

Multiple wireless devices may perform Msg 1 1220, for example, bysending (e.g., transmitting) the same preamble to a base station. Themultiple wireless devices may receive, from the base station, the samerandom access response comprising an identity (e.g., TC-RNTI).Contention resolution (e.g., comprising the wireless device 110receiving contention resolution 1250) may be used to increase thelikelihood that a wireless device does not incorrectly use an identityof another wireless device. The contention resolution 1250 may be basedon, for example, a C-RNTI on a PDCCH, and/or a wireless devicecontention resolution identity on a DL-SCH. If a base station assigns aC-RNTI to a wireless device, the wireless device may perform contentionresolution (e.g., comprising receiving contention resolution 1250), forexample, based on a reception of a PDCCH transmission that is addressedto the C-RNTI. The wireless device may determine that contentionresolution is successful, and/or that a random access procedure issuccessfully completed, for example, after or in response to detecting aC-RNTI on a PDCCH. If a wireless device has no valid C-RNTI, acontention resolution may be addressed by using a TC-RNTI. If a MAC PDUis successfully decoded and a MAC PDU comprises a wireless devicecontention resolution identity MAC CE that matches or otherwisecorresponds with the CCCH SDU sent (e.g., transmitted) in Msg3 1250, thewireless device may determine that the contention resolution (e.g.,comprising contention resolution 1250) is successful and/or the wirelessdevice may determine that the random access procedure is successfullycompleted.

FIG. 13 shows an example structure for MAC entities. A wireless devicemay be configured to operate in a multi-connectivity mode. A wirelessdevice in RRC_CONNECTED with multiple Rx/Tx may be configured to utilizeradio resources provided by multiple schedulers that may be located in aplurality of base stations. The plurality of base stations may beconnected via a non-ideal or ideal backhaul over the Xn interface. Abase station in a plurality of base stations may act as a master basestation or as a secondary base station. A wireless device may beconnected to and/or in communication with, for example, one master basestation and one or more secondary base stations. A wireless device maybe configured with multiple MAC entities, for example, one MAC entityfor a master base station, and one or more other MAC entities forsecondary base station(s). A configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 shows an example structurefor MAC entities in which a MCG and a SCG are configured for a wirelessdevice.

At least one cell in a SCG may have a configured UL CC. A cell of the atleast one cell may comprise a PSCell or a PCell of a SCG, or a PCell. APSCell may be configured with PUCCH resources. There may be at least oneSCG bearer, or one split bearer, for a SCG that is configured. After orupon detection of a physical layer problem or a random access problem ona PSCell, after or upon reaching a number of RLC retransmissionsassociated with the SCG, and/or after or upon detection of an accessproblem on a PSCell associated with (e.g., during) a SCG addition or aSCG change: an RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of a SCG may be stopped,and/or a master base station may be informed by a wireless device of aSCG failure type and DL data transfer over a master base station may bemaintained.

A MAC sublayer may provide services such as data transfer and radioresource allocation to upper layers (e.g., 1310 or 1320). A MAC sublayermay comprise a plurality of MAC entities (e.g., 1350 and 1360). A MACsublayer may provide data transfer services on logical channels. Toaccommodate different kinds of data transfer services, multiple types oflogical channels may be defined. A logical channel may support transferof a particular type of information. A logical channel type may bedefined by what type of information (e.g., control or data) istransferred. BCCH, PCCH, CCCH and/or DCCH may be control channels, andDTCH may be a traffic channel. A first MAC entity (e.g., 1310) mayprovide services on PCCH, BCCH, CCCH, DCCH, DTCH, and/or MAC controlelements. A second MAC entity (e.g., 1320) may provide services on BCCH,DCCH, DTCH, and/or MAC control elements.

A MAC sublayer may expect from a physical layer (e.g., 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,and/or signaling of scheduling request or measurements (e.g., CQI). Indual connectivity, two MAC entities may be configured for a wirelessdevice: one for a MCG and one for a SCG. A wireless device (e.g., a MACentity of the wireless device) may handle a plurality of transportchannels. A first MAC entity may handle first transport channelscomprising a PCCH of a MCG, a first BCH of the MCG, one or more firstDL-SCHs of the MCG, one or more first UL-SCHs of the MCG, and/or one ormore first RACHs of the MCG. A second MAC entity may handle secondtransport channels comprising a second BCH of a SCG, one or more secondDL-SCHs of the SCG, one or more second UL-SCHs of the SCG, and/or one ormore second RACHs of the SCG.

If a MAC entity is configured with one or more SCells, there may bemultiple DL-SCHs, multiple UL-SCHs, and/or multiple RACHs per MACentity. There may be one DL-SCH and/or one UL-SCH on an SpCell. Theremay be one DL-SCH, zero or one UL-SCH, and/or zero or one RACH for anSCell. A DL-SCH may support receptions using different numerologiesand/or TTI duration within a MAC entity. A UL-SCH may supporttransmissions using different numerologies and/or TTI duration withinthe MAC entity.

A MAC sublayer may support different functions. The MAC sublayer maycontrol these functions with a control (e.g., Control 1355 and/orControl 1365) element. Functions performed by a MAC entity may compriseone or more of: mapping between logical channels and transport channels(e.g., in uplink or downlink), multiplexing (e.g., (De-) Multiplexing1352 and/or (De-) Multiplexing 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TBs) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g., (De-) Multiplexing 1352 and/or (De-) Multiplexing 1362) of MACSDUs to one or different logical channels from transport blocks (TBs)delivered from the physical layer on transport channels (e.g., indownlink), scheduling information reporting (e.g., in uplink), errorcorrection through HARQ in uplink and/or downlink (e.g., 1363), andlogical channel prioritization in uplink (e.g., Logical ChannelPrioritization 1351 and/or Logical Channel Prioritization 1361). A MACentity may handle a random access process (e.g., Random Access Control1354 and/or Random Access Control 1364).

FIG. 14 shows an example of a RAN architecture comprising one or morebase stations. A protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and/orPHY) may be supported at a node. A base station (e.g., gNB 120A and/or120B) may comprise a base station central unit (CU) (e.g., gNB-CU 1420Aor 1420B) and at least one base station distributed unit (DU) (e.g.,gNB-DU 1430A, 1430B, 1430C, and/or 1430D), for example, if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g., CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. An Xn interface may be configured between base stationCUs.

A base station CU may comprise an RRC function, an SDAP layer, and/or aPDCP layer. Base station DUs may comprise an RLC layer, a MAC layer,and/or a PHY layer. Various functional split options between a basestation CU and base station DUs may be possible, for example, bylocating different combinations of upper protocol layers (e.g., RANfunctions) in a base station CU and different combinations of lowerprotocol layers (e.g., RAN functions) in base station DUs. A functionalsplit may support flexibility to move protocol layers between a basestation CU and base station DUs, for example, depending on servicerequirements and/or network environments.

Functional split options may be configured per base station, per basestation CU, per base station DU, per wireless device, per bearer, perslice, and/or with other granularities. In a per base station CU split,a base station CU may have a fixed split option, and base station DUsmay be configured to match a split option of a base station CU. In a perbase station DU split, a base station DU may be configured with adifferent split option, and a base station CU may provide differentsplit options for different base station DUs. In a per wireless devicesplit, a base station (e.g., a base station CU and at least one basestation DUs) may provide different split options for different wirelessdevices. In a per bearer split, different split options may be utilizedfor different bearers. In a per slice splice, different split optionsmay be used for different slices.

FIG. 15 shows example RRC state transitions of a wireless device. Awireless device may be in at least one RRC state among an RRC connectedstate (e.g., RRC Connected 1530, RRC_Connected, etc.), an RRC idle state(e.g., RRC Idle 1510, RRC_Idle, etc.), and/or an RRC inactive state(e.g., RRC Inactive 1520, RRC_Inactive, etc.). In an RRC connectedstate, a wireless device may have at least one RRC connection with atleast one base station (e.g., gNB and/or eNB), which may have a contextof the wireless device (e.g., UE context). A wireless device context(e.g., UE context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.,data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an RRC idle state, a wireless device may not have an RRCconnection with a base station, and a context of the wireless device maynot be stored in a base station. In an RRC inactive state, a wirelessdevice may not have an RRC connection with a base station. A context ofa wireless device may be stored in a base station, which may comprise ananchor base station (e.g., a last serving base station).

A wireless device may transition an RRC state (e.g., UE RRC state)between an RRC idle state and an RRC connected state in both ways (e.g.,connection release 1540 or connection establishment 1550; and/orconnection reestablishment) and/or between an RRC inactive state and anRRC connected state in both ways (e.g., connection inactivation 1570 orconnection resume 1580). A wireless device may transition its RRC statefrom an RRC inactive state to an RRC idle state (e.g., connectionrelease 1560).

An anchor base station may be a base station that may keep a context ofa wireless device (e.g., UE context) at least at (e.g., during) a timeperiod that the wireless device stays in a RAN notification area (RNA)of an anchor base station, and/or at (e.g., during) a time period thatthe wireless device stays in an RRC inactive state. An anchor basestation may comprise a base station that a wireless device in an RRCinactive state was most recently connected to in a latest RRC connectedstate, and/or a base station in which a wireless device most recentlyperformed an RNA update procedure. An RNA may comprise one or more cellsoperated by one or more base stations. A base station may belong to oneor more RNAs. A cell may belong to one or more RNAs.

A wireless device may transition, in a base station, an RRC state (e.g.,UE RRC state) from an RRC connected state to an RRC inactive state. Thewireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

An anchor base station may broadcast a message (e.g., RAN pagingmessage) to base stations of an RNA to reach to a wireless device in anRRC inactive state. The base stations receiving the message from theanchor base station may broadcast and/or multicast another message(e.g., paging message) to wireless devices in their coverage area, cellcoverage area, and/or beam coverage area associated with the RNA via anair interface.

A wireless device may perform an RNA update (RNAU) procedure, forexample, if the wireless device is in an RRC inactive state and movesinto a new RNA. The RNAU procedure may comprise a random accessprocedure by the wireless device and/or a context retrieve procedure(e.g., UE context retrieve). A context retrieve procedure may comprise:receiving, by a base station from a wireless device, a random accesspreamble; and requesting and/or receiving (e.g., fetching), by a basestation, a context of the wireless device (e.g., UE context) from an oldanchor base station. The requesting and/or receiving (e.g., fetching)may comprise: sending a retrieve context request message (e.g., UEcontext request message) comprising a resume identifier to the oldanchor base station and receiving a retrieve context response messagecomprising the context of the wireless device from the old anchor basestation.

A wireless device in an RRC inactive state may select a cell to camp onbased on at least a measurement result for one or more cells, a cell inwhich a wireless device may monitor an RNA paging message, and/or a corenetwork paging message from a base station. A wireless device in an RRCinactive state may select a cell to perform a random access procedure toresume an RRC connection and/or to send (e.g., transmit) one or morepackets to a base station (e.g., to a network). The wireless device mayinitiate a random access procedure to perform an RNA update procedure,for example, if a cell selected belongs to a different RNA from an RNAfor the wireless device in an RRC inactive state. The wireless devicemay initiate a random access procedure to send (e.g., transmit) one ormore packets to a base station of a cell that the wireless deviceselects, for example, if the wireless device is in an RRC inactive stateand has one or more packets (e.g., in a buffer) to send (e.g., transmit)to a network. A random access procedure may be performed with twomessages (e.g., 2-stage or 2-step random access) and/or four messages(e.g., 4-stage or 4-step random access) between the wireless device andthe base station.

A base station receiving one or more uplink packets from a wirelessdevice in an RRC inactive state may request and/or receive (e.g., fetch)a context of a wireless device (e.g., UE context), for example, bysending (e.g., transmitting) a retrieve context request message for thewireless device to an anchor base station of the wireless device basedon at least one of an AS context identifier, an RNA identifier, a basestation identifier, a resume identifier, and/or a cell identifierreceived from the wireless device. A base station may send (e.g.,transmit) a path switch request for a wireless device to a core networkentity (e.g., AMF, MME, and/or the like), for example, after or inresponse to requesting and/or receiving (e.g., fetching) a context. Acore network entity may update a downlink tunnel endpoint identifier forone or more bearers established for the wireless device between a userplane core network entity (e.g., UPF, S-GW, and/or the like) and a RANnode (e.g., the base station), such as by changing a downlink tunnelendpoint identifier from an address of the anchor base station to anaddress of the base station).

A base station may communicate with a wireless device via a wirelessnetwork using one or more technologies, such as new radio technologies(e.g., NR, 5G, etc.). The one or more radio technologies may comprise atleast one of: multiple technologies related to physical layer; multipletechnologies related to medium access control layer; and/or multipletechnologies related to radio resource control layer Enhancing the oneor more radio technologies may improve performance of a wirelessnetwork. System throughput, and/or data rate of transmission, may beincreased. Battery consumption of a wireless device may be reduced.Latency of data transmission between a base station and a wirelessdevice may be improved. Network coverage of a wireless network may beimproved. Transmission efficiency of a wireless network may be improved.

A base station may send (e.g., transmit) DCI via a PDCCH for at leastone of: a scheduling assignment and/or grant; a slot formatnotification; a preemption indication; and/or a power-control command.The DCI may comprise at least one of: an identifier of a DCI format; adownlink scheduling assignment(s); an uplink scheduling grant(s); a slotformat indicator; a preemption indication; a power-control forPUCCH/PUSCH; and/or a power-control for SRS.

A downlink scheduling assignment DCI may comprise parameters indicatingat least one of: an identifier of a DCI format; a PDSCH resourceindication; a transport format; HARQ information; control informationrelated to multiple antenna schemes; and/or a command for power controlof the PUCCH. An uplink scheduling grant DCI may comprise parametersindicating at least one of: an identifier of a DCI format; a PUSCHresource indication; a transport format; HARQ related information;and/or a power control command of the PUSCH.

Different types of control information may correspond to different DCImessage sizes. Supporting multiple beams, spatial multiplexing in thespatial domain, and/or noncontiguous allocation of RBs in the frequencydomain, may require a larger scheduling message, in comparison with anuplink grant allowing for frequency-contiguous allocation. DCI may becategorized into different DCI formats. A DCI format may correspond to acertain message size and/or usage.

A wireless device may monitor (e.g., in common search space or wirelessdevice-specific search space) one or more PDCCH for detecting one ormore DCI with one or more DCI format. A wireless device may monitor aPDCCH with a limited set of DCI formats, for example, which may reducepower consumption. The more DCI formats that are to be detected, themore power may be consumed by the wireless device.

The information in the DCI formats for downlink scheduling may compriseat least one of: an identifier of a DCI format; a carrier indicator; afrequency domain resource assignment; a time domain resource assignment;a time resource allocation; a bandwidth part indicator; a HARQ processnumber; one or more MCS; one or more NDI; one or more RV; MIMO relatedinformation; a downlink assignment index (DAI); PUCCH resourceindicator; PDSCH-to-HARQ feedback timing indicator; a TPC for PUCCH; anSRS request; and/or padding (e.g., if necessary). The MIMO relatedinformation may comprise at least one of: a PMI; precoding information;a transport block swap flag; a power offset between PDSCH and areference signal; a reference-signal scrambling sequence; a number oflayers; antenna ports for the transmission; and/or a transmissionconfiguration indication (TCI).

The information in the DCI formats used for uplink scheduling maycomprise at least one of: an identifier of a DCI format; a carrierindicator; a bandwidth part indication; a resource allocation type; afrequency domain resource assignment; a time domain resource assignment;a time resource allocation; an MCS; an NDI; a phase rotation of theuplink DMRS; precoding information; a CSI request; an SRS request; anuplink index/DAI; a TPC for PUSCH; and/or padding (e.g., if necessary).

A base station may perform CRC scrambling for DCI, for example, beforetransmitting the DCI via a PDCCH message. The base station may performCRC scrambling by binary addition of multiple bits of at least onewireless device identifier (e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI,TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SP CSI C-RNTI, and/or TPC-SRS-RNTI) andthe CRC bits of the DCI. The wireless device may check the CRC bits ofthe DCI, for example, if detecting the DCI. The wireless device mayreceive the DCI, for example, if the CRC is scrambled by a sequence ofbits that is the same as the at least one wireless device identifier.

A base station may send (e.g., transmit) one or more PDCCH messages indifferent CORESETs, for example, to support a wide bandwidth operation.A base station may transmit one or more RRC messages comprisingconfiguration parameters of one or more CORESETs. A CORESET may compriseat least one of: a first OFDM symbol; a number of consecutive OFDMsymbols; a set of resource blocks; and/or a CCE-to-REG mapping. A basestation may send (e.g., transmit) a PDCCH message in a dedicated CORESETfor particular purpose, for example, for beam failure recoveryconfirmation. A wireless device may monitor a PDCCH for detecting DCI inone or more configured CORESETs, for example, to reduce the powerconsumption.

A base station may send (e.g., transmit) one or more MAC PDUs to awireless device. A MAC PDU may comprise a bit string that may be bytealigned (e.g., multiple of eight bits) in length. Bit strings may berepresented by tables in which the most significant bit is the leftmostbit of the first line of the table, and the least significant bit is therightmost bit on the last line of the table. The bit string may be readfrom the left to right, and then, in the reading order of the lines. Thebit order of a parameter field within a MAC PDU may be represented withthe first and most significant bit in the leftmost bit, and with thelast and least significant bit in the rightmost bit.

A MAC SDU may comprise a bit string that is byte aligned (e.g., multipleof eight bits) in length. A MAC SDU may be included in a MAC PDU, forexample, from the first bit onward. A MAC CE may be a bit string that isbyte aligned (e.g., multiple of eight bits) in length. A MAC subheadermay be a bit string that is byte aligned (e.g., multiple of eight bits)in length. A MAC subheader may be placed immediately in front of thecorresponding MAC SDU, MAC CE, and/or padding. A MAC entity may ignore avalue of reserved bits in a DL MAC PDU.

A MAC PDU may comprise one or more MAC subPDUs. A MAC subPDU of the oneor more MAC subPDUs may comprise at least one of: a MAC subheader only(e.g., including padding); a MAC subheader and a MAC SDU; a MACsubheader and a MAC CE; and/or a MAC subheader and padding. The MAC SDUmay be of variable size. A MAC subheader may correspond to a MAC SDU, aMAC CE, and/or padding.

A MAC subheader may comprise: an R field comprising one bit; an F fieldwith one bit in length; an LCID field with multiple bits in length; an Lfield with multiple bits in length, for example, if the MAC subheadercorresponds to a MAC SDU, a variable-sized MAC CE, and/or padding.

A MAC subheader may comprise an eight-bit L field. The LCID field mayhave six bits in length, and the L field may have eight bits in length.A MAC subheader may comprise a sixteen-bit L field. The LCID field maybe six bits in length, and the L field may be sixteen bits in length.

A MAC subheader may comprise: an R field with two bits in length; and anLCID field with multiple bits in length, when the MAC subheadercorresponds to a fixed sized MAC CE, or padding. The LCID field may havesix bits in length, and the R field may have two bits in length.

DL MAC PDU, multiple MAC CEs may be placed together. A MAC subPDUcomprising MAC CE may be placed before any MAC subPDU comprising a MACSDU, or a MAC subPDU comprising padding.

UL MAC PDU, multiple MAC CEs may be placed together. A MAC subPDUcomprising MAC CE may be placed after all MAC subPDU comprising a MACSDU. The MAC subPDU may be placed before a MAC subPDU comprisingpadding.

A base station (e.g. a MAC entity of the base station) may send (e.g.,transmit) to a MAC entity of a wireless device one or more MAC CEs. Theone or more MAC CEs may comprise at least one of: an SP ZP CSI-RSResource Set Activation/Deactivation MAC CE; a PUCCH spatial relationActivation/Deactivation MAC CE; a SP SRS Activation/Deactivation MAC CE;a SP CSI reporting on PUCCH Activation/Deactivation MAC CE; a TCI StateIndication for UE-specific PDCCH MAC CE; a TCI State Indication forUE-specific PDSCH MAC CE; an Aperiodic CSI Trigger State SubselectionMAC CE; a SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE;a wireless device (e.g., UE) contention resolution identity MAC CE; atiming advance command MAC CE; a DRX command MAC CE; a long DRX commandMAC CE; an SCell activation and/or deactivation MAC CE (e.g., 1 Octet);an SCell activation and/or deactivation MAC CE (e.g., 4 Octet); and/or aduplication activation and/or deactivation MAC CE. A MAC CE may comprisean LCID in the corresponding MAC subheader. Different MAC CEs may havedifferent LCID in the corresponding MAC subheader. An LCID with 111011in a MAC subheader may indicate a MAC CE associated with the MACsubheader is a long DRX command MAC CE.

The wireless device (e.g., the MAC entity of the wireless device) maysend (e.g., transmit), to the base station (e.g., the MAC entity of thebase station), one or more MAC CEs. The one or more MAC CEs may compriseat least one of: a short buffer status report (BSR) MAC CE; a long BSRMAC CE; a C-RNTI MAC CE; a configured grant confirmation MAC CE; asingle entry power headroom report (PHR) MAC CE; a multiple entry PHRMAC CE; a short truncated BSR; and/or a long truncated BSR. A MAC CE maycomprise an LCID in the corresponding MAC subheader. Different MAC CEsmay have different LCIDs in the corresponding MAC subheader. The LCIDwith 111011 in a MAC subheader may indicate a MAC CE associated with theMAC subheader is a short-truncated command MAC CE.

Two or more component carriers (CCs) may be aggregated, for example, ina carrier aggregation (CA). A wireless device may simultaneously receiveand/or transmit on one or more CCs, for example, depending oncapabilities of the wireless device. The CA may be supported forcontiguous CCs. The CA may be supported for non-contiguous CCs.

A wireless device may have one RRC connection with a network, forexample, if configured with CA. At (e.g., during) an RRC connectionestablishment, re-establishment and/or handover, a cell providing a NASmobility information may be a serving cell. At (e.g., during) an RRCconnection re-establishment and/or handover procedure, a cell providinga security input may be a serving cell. The serving cell may be referredto as a primary cell (PCell). A base station may send (e.g., transmit),to a wireless device, one or more messages comprising configurationparameters of a plurality of one or more secondary cells (SCells), forexample, depending on capabilities of the wireless device.

A base station and/or a wireless device may use an activation and/ordeactivation mechanism of an SCell for an efficient battery consumption,for example, if the base station and/or the wireless device isconfigured with CA. A base station may activate or deactivate at leastone of the one or more SCells, for example, if the wireless device isconfigured with one or more SCells. The SCell may be deactivated, forexample, after or upon configuration of an SCell.

A wireless device may activate and/or deactivate an SCell, for example,after or in response to receiving an SCell activation and/ordeactivation MAC CE. A base station may send (e.g., transmit), to awireless device, one or more messages comprising ansCellDeactivationTimer timer. The wireless device may deactivate anSCell, for example, after or in response to an expiry of thesCellDeactivationTimer timer.

A wireless device may activate an SCell, for example, if the wirelessdevice receives an SCell activation/deactivation MAC CE activating anSCell. The wireless device may perform operations (e.g., after or inresponse to the activating the SCell) that may comprise: SRStransmissions on the SCell; CQI, PMI, RI, and/or CRI reporting for theSCell on a PCell; PDCCH monitoring on the SCell; PDCCH monitoring forthe SCell on the PCell; and/or PUCCH transmissions on the SCell.

The wireless device may start and/or restart a timer (e.g., ansCellDeactivationTimer timer) associated with the SCell, for example,after or in response to activating the SCell. The wireless device maystart the timer (e.g., sCellDeactivationTimer timer) in the slot, forexample, if the SCell activation/deactivation MAC CE has been received.The wireless device may initialize and/or re-initialize one or moresuspended configured uplink grants of a configured grant Type 1associated with the SCell according to a stored configuration, forexample, after or in response to activating the SCell. The wirelessdevice may trigger a PHR, for example, after or in response toactivating the SCell.

The wireless device may deactivate the activated SCell, for example, ifthe wireless device receives an SCell activation/deactivation MAC CEdeactivating an activated SCell. The wireless device may deactivate theactivated SCell, for example, if a timer (e.g., ansCellDeactivationTimer timer) associated with an activated SCellexpires. The wireless device may stop the BWP inactivity timerassociated with the activated SCell, for example, after or in responseto deactivating the activated SCell. The wireless device may deactivatean active BWP associated with the activated SCell, for example, after orin response to deactivating the activated SCell. The wireless device maystop the timer (e.g., sCellDeactivationTimer timer) associated with theactivated SCell, for example, after or in response to deactivating theactivated SCell. The wireless device may clear one or more configureddownlink assignments and/or one or more configured uplink grant (e.g.,Type 2) associated with the activated SCell, for example, after or inresponse to deactivating the activated SCell. The wireless device maysuspend one or more configured uplink grant (e.g., Type 1) associatedwith the activated SCell, for example, after or in response todeactivating the activated SCell. The wireless device may flush HARQbuffers associated with the activated SCell.

A wireless device may not perform certain operations, for example, if anSCell is deactivated. The wireless device may not perform one or more ofthe following operations if an SCell is deactivated: transmitting SRS onthe SCell; reporting CQI, PMI, RI, and/or CRI for the SCell on a PCell;transmitting on UL-SCH on the SCell; transmitting on a RACH on theSCell; monitoring at least one first PDCCH on the SCell; monitoring atleast one second PDCCH for the SCell on the PCell; and/or transmitting aPUCCH on the SCell.

A wireless device may restart a timer (e.g., an sCellDeactivationTimertimer) associated with the activated SCell, for example, if at least onefirst PDCCH on an activated SCell indicates an uplink grant or adownlink assignment. A wireless device may restart a timer (e.g., ansCellDeactivationTimer timer) associated with the activated SCell, forexample, if at least one second PDCCH on a serving cell (e.g. a PCell oran SCell configured with PUCCH, such as a PUCCH SCell) scheduling theactivated SCell indicates an uplink grant and/or a downlink assignmentfor the activated SCell. A wireless device may abort the ongoing randomaccess procedure on the SCell, for example, if an SCell is deactivatedand/or if there is an ongoing random access procedure on the SCell.

An SCell activation/deactivation MAC CE may comprise, for example, oneoctet. A first MAC PDU subheader comprising a first LCID may identifythe SCell activation/deactivation MAC CE of one octet. An SCellactivation/deactivation MAC CE of one octet may have a fixed size. TheSCell activation/deactivation MAC CE of one octet may comprise a singleoctet. The single octet may comprise a first number of C-fields (e.g.,seven) and a second number of R-fields (e.g., one).

An SCell Activation/Deactivation MAC CE may comprise, for example, anysize such as any quantity of octets (e.g., four octets). A second MACPDU subheader with a second LCID may identify the SCellActivation/Deactivation MAC CE of four octets. An SCellactivation/deactivation MAC CE of four octets may have a fixed size. TheSCell activation/deactivation MAC CE of four octets may comprise fouroctets. The four octets may comprise a third number of C-fields (e.g.,31) and a fourth number of R-fields (e.g., 1). A C_(i) field mayindicate an activation/deactivation status of an SCell with an SCellindex i, for example, if an SCell with SCell index i is configured. AnSCell with an SCell index i may be activated, for example, if the C_(i)field is set to one. An SCell with an SCell index i may be deactivated,for example, if the C_(i) field is set to zero. The wireless device mayignore the C_(i) field, for example, if there is no SCell configuredwith SCell index i. An R field may indicate a reserved bit. The R fieldmay be set to zero.

A base station may configure a wireless device with one or moreTCI-states using, and/or via, a higher layer parameter (e.g.,PDSCH-Config) for a serving cell. A quantity (e.g., number, plurality,etc.) of the one or more TCI-states may depend on a capability of thewireless device. The wireless device may use the one or more TCI-statesto decode a PDSCH based on a detected PDCCH with a DCI. The DCI may beintended for the wireless device and the serving cell. Each of the oneor more TCI-states state may contain one or more parameters. The one ormore parameters may configure a quasi co-location relationship betweenone or more downlink reference signals (e.g., first DL RS and second RLRS) and the DM-RS ports of the PDSCH. The quasi co-location may beconfigured by a higher layer parameter (e.g., QCL-Type1) for the firstDL RS. The quasi co-location relationship may be configured by a higherlayer parameter (e.g., QCL-Type2) for the second DL-RS (if configured).QCL-Types associated with the two DL RSs may not necessarily be thesame, for example, if the one RS set contains a reference to the two DLRSs. The references of the two DL RSs may be, for example, to a same DLRS or to different DL RSs. The QCL-Types corresponding to each DL RS maybe conveyed to the wireless device by a higher layer parameter (e.g.,QCL-Type in QCL-Info). The higher layer parameter QCL-Type may compriseat least one of the following types: QCL-TypeA′: {Doppler shift, Dopplerspread, average delay, delay spread}, QCL-TypeB′: {Doppler shift,Doppler spread}, QCL-TypeC′: {average delay, Doppler shift} andQCL-TypeD′: {Spatial Rx parameter}.

A wireless device may receive an activation command that may be used tomap one or more TCI-states (e.g., 8) to one or more codepoints of a TCIfield in DCI. If a HARQ-ACK corresponding to a PDSCH carrying theactivation commend is transmitted in slot n, the indicated mappingbetween one or more TCI-states and one or more codepoints of the DCIfield “Transmission Configuration Indication” may be applied from slot

n+3N _(Slot) ^(subfram,μ)+1.

The wireless device may determine (e.g., assume) that one or more DM-RSports of PDSCH of a serving cell are quasi co-located with an SSB/PBCHblock, for example, (i) before the wireless device receives theactivation command and/or (ii) after the wireless device receives ahigher layer configuration of TCI-states. The wireless device and/or thebase station may determine the SSB/PBCH block in an initial accessprocedure with respect to “QCL-TypeA,” and with respect to “QCL-TypeD,”if applicable.

A wireless device may be configured, by a base station, with a higherlayer parameter (e.g., TCI-PresentinDCI). The wireless device maydetermine (e.g., assume) that a TCI field is present in a DCI format(e.g., DCI format 1_1) of a PDCCH message transmitted on a CORESET, forexample, if the higher layer parameter (e.g., TCI-PresentInDCI) isenabled (e.g., set as “Enabled”) for the CORESET scheduling the PDSCH.

A wireless device may determine (e.g., assume) that a first TCI statefor the PDSCH is identical to a second TCI state applied for the CORESETused for the PDCCH transmission, for example, to determine PDSCH antennaport quasi co-location. A first TCI state may be identical to a secondTCI state, for example, if a higher layer parameter (e.g.,TCI-PresentinDCI) is not configured for a CORESET scheduling a PDSCH.The first TCI state may be identical to a second TCI state, if a PDSCHis scheduled by a DCI format (e.g., DCI format 1_0). A TCI field in ascheduling component carrier of a DCI may indicate to one or moreactivated TCI-states in a scheduled component carrier or a DL BWP, forexample, if a higher layer parameter (e.g., TCI-PresentDCI) is enabled(e.g., set as “Enabled”). The wireless device may use one or moreTCI-states according to a value of a TCI field in a detected PDCCH withDCI for determining PDSCH antenna port quasi co-location, for example,if the higher layer parameter TCI-PresentInDCI is enabled (e.g., set as“Enabled”) and if a PDSCH is scheduled by a DCI format (e.g., DCI format1_1). The wireless device may determine (e.g., assume) that antennaports of one DM-RS port group of a PDSCH of a serving cell are quasico-located with one or more RS(s) in a TCI-state with respect to QCLtype parameter(s) given by the indicated TCI state, for example, if atime offset between the reception of the DL DCI and the correspondingPDSCH is equal to or greater than a threshold (e.g.,Threshold-Sched-Offset). The threshold (e.g., Threshold-Sched-Offset)may be based on, for example, wireless device capability. The indicatedTCI state may be based on the activated TCI-states in the slot in thescheduled PDSCH, for example, if the wireless device is configured witha single slot PDSCH. The wireless device may determine (e.g., assume)that one or more DM-RS ports of PDSCH of a serving cell are quasico-located with one or more RSs in a TCI state with respect to QCL typeparameter(s). The QCL type parameter(s) may be used for PDCCH quasico-location indication of the lowest CORESET-ID in the latest slot. Inthe latest slot, one or more CORESETs within an active BWP of theservice cell may be configured for the wireless device, for example, if(i) the offset between reception of the DL DCI and the correspondingPDSCH is less than a threshold Threshold-Sched-Offset and/or if (ii) thehigher layer parameter (e.g., TCI-PresentInDCI) is enabled (e.g., set to“Enabled”) or the higher layer parameter (e.g., TCI-PresentInDCI) is notconfigured in RRC connected mode. The wireless device may obtain theother QCL assumptions from the indicated TCI-states for its scheduledPDSCH, for example, irrespective of a time offset between the receptionof the DL DCI and the corresponding PDSCH, if none of the configuredTCI-states define a type of quasi-co-location (e.g., QCL-TypeD).

A wireless device may be provided (e.g., by a higher layer signaling)with one or more (e.g., 3) CORESETS for a DL BWP configured for thewireless device in a serving cell. For a first CORESET of the one ormore CORESETS, the wireless device may be provided a higher layerparameter (e.g., ControlResourceSet). The higher layer parameter may beat least one of: a CORESET index (e.g., controlResourceSetId), a DMRSscrambling sequence initialization value, a number of consecutivesymbols (e.g., duration), a set of resource blocks (e.g.,frequencyDomainResources), CCE-to-REG mapping parameters (e.g.,cce-REG-MappingType), an antenna port quasi co-location (e.g.,TCI-states), and an indication for a presence or absence of atransmission configuration indication (TCI) field (e.g.,TCI-PresentInDCI). The antenna port quasi co-location may indicate quasico-location information of the DM-RS antenna port for PDCCH reception inthe first CORESET.

A wireless device may determine (e.g., assume) that the DM-RS antennaport associated with the PDCCH receptions is quasi co-located with aSS/PBCH block, for example, if the wireless device has received initialconfiguration of a plurality of TCI-states for PDCCH receptions byhigher layer parameter TCI-states but has not received a MAC CEactivation command for one of the plurality of the TCI-states. Thewireless device may identify the SS/PBCH block during an initial accessprocedure.

A wireless device may receive higher layer parameter TCI-states forPDCCH receptions. The higher layer parameter TCI-states may contain asingle TCI state. The wireless device may determine (e.g., assume) thatthe DM-RS antenna port associated with the PDCCH receptions is quasico-located with the one or more DL RS configured by the single TCIstate, for example, after or in response to the higher layer parameterTCI-states containing the single TCI state.

A wireless device may be provided by higher layers with one or more(e.g., 3, 5, 10, etc.) search space sets for a DL BWP configured for thewireless device in a serving cell. The wireless device may be provided ahigher layer parameter (e.g., SearchSpace), for example, for a firstsearch space set of the one or more search space sets. The higher layerparameter may be at least one of: a search space set index (e.g.,searchSpaceId), an association between the search space set and acontrol resource set (e.g., controlResourceSetId); an indication thatthe search space set is a common search space set; and/or an indicationthat the search space set is a wireless device-specific search space set(e.g., searchSpaceType).

A base station may indicate, to a wireless device, a TCI state for aCORESET of a serving cell. The base station may indicate the TCI stateby sending a TCI state indication via a wireless device-specific PDCCHMAC CE. The TCI state may indicate a PDCCH reception for the CORESET ofthe serving cell. A wireless device (e.g., a MAC entity of the wirelessdevice) may provide one or more lower layers (e.g., PHY) with theinformation regarding the TCI state indication for a wirelessdevice-specific PDCCH MAC CE. The wireless device (e.g. the MAC entityof the wireless device) may provide the information regarding the TCIstate indication, for example, if the wireless device (e.g., the MACentity of the wireless device) receives a TCI state indication via thewireless device-specific PDCCH MAC CE on, or for, a serving cell. TheTCI state indication for the wireless device-specific PDCCH MAC CE maybe identified and/or indicated by a MAC PDU subheader with LCID. The TCIstate indication may have a fixed size of bits (e.g., 16 bits) and maycomprise one or more fields, such as serving cell ID, CORESET ID, TCIstate ID, and a reserved bit. The serving cell ID may indicate theidentity of the serving cell for which the TCI state indication applies.The length of the serving cell ID may be n bits (e.g., n=5 bits). TheCORESET ID (e.g., ControlResourceSetId) may indicate a CORESET. Thelength of the CORESET ID may be n₂ bits (e.g., n₂=4 bits). The TCI stateID (e.g., TCI-StateId) may indicate the TCI state and may be applicableto the CORESET identified and/or indicated by the CORESET ID. The lengthof the TCI state ID may be n₃ bits (e.g., n₃=6 bits).

An information element (e.g., ControlResourceSet) may be used toconfigure a time/frequency CORESET in which to search for downlinkcontrol information (DCI). An information element (e.g., TCI-State) mayassociate one or two DL reference signals with a corresponding QCL type.The information element TCI-state may comprise one or more fieldsincluding TCI-StateId and QCL-Info. QCL-Info may comprise one or moresecond fields, including, for example, serving cell index, BWP ID, areference signal index (e.g., SSB-index, NZP-CSI-RS-ResourceID), and aQCL Type (e.g., QCL-typeA, QCL-typeB, QCL-typeC, QCL-typeD). The servingcell index may indicate the carrier in which a reference signal (RS)associated with the reference signal index is located in. Theinformation element TCI-state may apply to a serving cell in which theinformation element TCI-state is configured, for example, if the servingcell index is absent in the information element TCI-state. The referencesignal may be located on a second serving cell, different from theserving cell in which the information element TCI-state is configured,if, for example, the QCL-Type is configured as QCL-typeD. An informationelement (e.g., SearchSpace) may define how and/or where to search forPDCCH candidates in a search space. The search space may be identifiedand/or indicated by a field (e.g., searchSpaceId) in the informationelement SearchSpace. Each search space may be associated with a CORESET(e.g., ControlResourceSet). The CORESET may be indicated (e.g.,identified) by a field (e.g., controlResourceSetId) in the informationelement SearchSpace, the field (e.g., controlResourceSetId) may indicatethe CORESET applicable for the SearchSpace.

A base station and/or a wireless device may have multiple antennas, forexample, to support a transmission with high data rate (such as in an NRsystem). A wireless device may perform one or more beam managementprocedures, as shown in FIG. 9B, for example, if configured withmultiple antennas.

A wireless device may perform a downlink beam management based on one ormore CSI-RSs and/or one or more SS blocks. In a beam managementprocedure, a wireless device may measure a channel quality of a beampair link. The beam pair link may comprise a transmitting beam from abase station and a receiving beam at the wireless device. A wirelessdevice may measure the multiple beam pair links between the base stationand the wireless device, for example, if the wireless device isconfigured with multiple beams associated with multiple CSI-RSs and/orSS blocks.

A wireless device may send (e.g., transmit) one or more beam managementreports to a base station. The wireless device may indicate one or morebeam pair quality parameters, for example, in a beam management report.The one or more beam pair quality parameters may comprise at least oneor more beam identifications; RSRP; and/or PMI, CQI, and/or RI of atleast a subset of configured multiple beams.

A base station and/or a wireless device may perform a downlink beammanagement procedure on one or multiple Transmission and Receiving Point(TRPs), such as shown in FIG. 9B. Based on a wireless device's beammanagement report, a base station may send (e.g., transmit), to thewireless device, a signal indicating that a new beam pair link is aserving beam. The base station may transmit PDCCH and/or PDSCH to thewireless device using the serving beam.

A wireless device and/or a base station may trigger a beam failurerecovery mechanism. A wireless device may trigger a beam failurerecovery (BFR) procedure, for example, if at least a beam failureoccurs. A beam failure may occur if a quality of beam pair link(s) of atleast one PDCCH falls below a threshold. The threshold comprise be anRSRP value (e.g., −140 dbm, −110 dbm, or any other value) and/or a SINRvalue (e.g., −3 dB, −1 dB, or any other value), which may be configuredin a RRC message.

FIG. 16A shows an example of a first beam failure event. A base station1602 may send (e.g., transmit) a PDCCH from a transmission (Tx) beam toa receiving (Rx) beam of a wireless device 1601 from a TRP. The basestation 1602 and the wireless device 1601 may start a beam failurerecovery procedure on the TRP, for example, if the PDCCH on the beampair link (e.g., between the Tx beam of the base station 1602 and the Rxbeam of the wireless device 1601) have a lower-than-threshold RSRPand/or SINR value due to the beam pair link being blocked (e.g., by amoving vehicle 1603, a building, or any other obstruction).

FIG. 16B shows an example of a second beam failure event. A base stationmay send (e.g., transmit) a PDCCH from a beam to a wireless device 1611from a first TRP 1614. The base station and the wireless device 1611 maystart a beam failure recovery procedure on a new beam on a second TRP1612, for example, if the PDCCH on the beam is blocked (e.g., by amoving vehicle 1613, building, or any other obstruction).

A wireless device may measure a quality of beam pair links using one ormore RSs. The one or more RSs may comprise one or more SS blocks and/orone or more CSI-RS resources. A CSI-RS resource may be determined by aCSI-RS resource index (CRI). A quality of beam pair links may beindicated by, for example, an RSRP value, a reference signal receivedquality (e.g., RSRQ) value, and/or a CSI (e.g., SINR) value measured onRS resources. A base station may indicate whether an RS resource, usedfor measuring beam pair link quality, is QCLed (Quasi-Co-Located) withDM-RSs of a PDCCH. The RS resource and the DM-RSs of the PDCCH may beQCLed, for example, if the channel characteristics from a transmissionon an RS to a wireless device, and that from a transmission on a PDCCHto the wireless device, are similar or same under a configuredcriterion. The RS resource and the DM-RSs of the PDCCH may be QCLed, forexample, if Doppler shift and/or Doppler shift of the channel from atransmission on an RS to a wireless device, and that from a transmissionon a PDCCH to the wireless device, are the same.

A wireless device may monitor a PDCCH on M beams (e.g. 2, 4, 8) pairlinks simultaneously, where M≥1 and the value of M may depend at leaston capability of the wireless device. Monitoring a PDCCH may comprisedetecting DCI via the PDCCH transmitted on common search spaces and/orwireless device specific search spaces. Monitoring multiple beam pairlinks may increase robustness against beam pair link blocking. A basestation may send (e.g., transmit) one or more messages comprisingparameters indicating a wireless device to monitor PDCCH on differentbeam pair link(s) in different OFDM symbols.

A base station may send (e.g., transmit) one or more RRC messages and/orMAC CEs comprising parameters indicating Rx beam setting of a wirelessdevice for monitoring PDCCH on multiple beam pair links. A base stationmay send (e.g., transmit) an indication of a spatial QCL between DL RSantenna port(s) and DL RS antenna port(s) for demodulation of DL controlchannel. The indication may comprise a parameter in a MAC CE, an RRCmessage, DCI, and/or any combinations of these signaling.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of DL data channel, for example, forreception of data packet on a PDSCH. A base station may send (e.g.,transmit) DCI comprising parameters indicating the RS antenna port(s)are QCLed with DM-RS antenna port(s).

A wireless device may measure a beam pair link quality based on CSI-RSsQCLed with DM-RS for PDCCH, for example, if a base station sends (e.g.,transmits) a signal indicating QCL parameters between CSI-RS and DM-RSfor PDCCH. The wireless device may start a BFR procedure, for example,if multiple contiguous beam failures occur.

A wireless device may send (e.g., transmit) a BFR signal on an uplinkphysical channel to a base station, for example, if starting a BFRprocedure. The base station may send (e.g., transmit) DCI via a PDCCH ina CORESET, for example, after or in response to receiving the BFR signalon the uplink physical channel. The wireless may determine that the BFRprocedure is successfully completed, for example, after or in responseto receiving the DCI via the PDCCH in the CORESET.

A base station may send (e.g., transmit) one or more messages comprisingconfiguration parameters of an uplink physical channel, or signal, fortransmitting a beam failure recovery request. The uplink physicalchannel or signal may be based on one of: a contention-free PRACH(BFR-PRACH), which may be a resource orthogonal to resources of otherPRACH transmissions; a PUCCH (e.g., BFR-PUCCH); and/or acontention-based PRACH resource (e.g., CF-PRACH). Combinations of thesecandidate signals and/or channels may be configured by the base station.A wireless device may autonomously select a first resource fortransmitting the BFR signal, for example, if the wireless device isconfigured with multiple resources for a BFR signal. The wireless devicemay select a BFR-PRACH resource for transmitting a BFR signal, forexample, if the wireless device is configured with the BFR-PRACHresource, a BFR-PUCCH resource, and/or a CF-PRACH resource. The basestation may send (e.g., transmit) a message to the wireless deviceindicating a resource for transmitting the BFR signal, for example, ifthe wireless device is configured with a BFR-PRACH resource, a BFR-PUCCHresource, and/or a CF-PRACH resource.

A base station may send (e.g., transmit) a response to a wirelessdevice, for example, after receiving one or more BFR signals. Theresponse may comprise the CRI associated with the candidate beam thatthe wireless device may indicate in the one or multiple BFR signals.

A base station and/or a wireless device may perform one or more beammanagement procedures, for example, if the base station and/or thewireless device are configured with multiple beams (e.g., in system suchas in an NR system). The wireless device may perform a BFR procedure(e.g., send one or more BFR signals), for example, if one or more beampair links between the base station and the wireless device fail.

A wireless device may receive one or more RRC messages that comprise BFRparameters. The one or more RRC messages may comprise one or more of anRRC connection reconfiguration message, an RRC connectionreestablishment message, and/or an RRC connection setup message. Thewireless device may detect at least one beam failure according to atleast one of BFR parameters and trigger a BFR procedure. The wirelessdevice may start a first timer, if configured, in response to detectingthe at least one beam failure. The wireless device may select a beam(e.g., a selected beam) in response to detecting the at least one beamfailure. The selected beam may be a beam with good channel quality(e.g., determined based on RSRP, SINR, or BLER, etc.) from a set ofcandidate beams. The set of candidate beams may be identified and/orindicated by a set of reference signals (e.g., SSBs, or CSI-RSs). Thewireless device may transmit at least a first BFR signal to a basestation in response to selecting the selected beam. The at least firstBFR signal may be associated with the selected beam. The at least firstBFR signal may be, for example, a preamble transmitted on a PRACHresource, or a beam failure request (e.g., which may be similar to anSR) signal transmitted on a PUCCH resource, or a beam indicationtransmitted on a PUCCH/PUSCH resource. The wireless device may transmitthe at least first BFR signal with a transmission beam corresponding toa receiving beam associated with the selected beam. The wireless device,may, for example, determine transmission beam by using the RF and/ordigital beamforming parameters corresponding to the receiving beam. Thewireless device may start a response window in response to transmittingthe at least first BFR signal. The response window may be tracked using,for example, a timer with a value configured by the base station. Thewireless device may monitor a PDCCH in a first CORESET while theresponse window is running. The first CORESET may be associated with theBFR procedure. The wireless device may monitor the PDCCH in the firstCORESET in condition of transmitting the at least first BFR signal. Thewireless device may receive a first DCI via the PDCCH in the firstCORESET while the response window is running. The wireless device mayconsider the BFR procedure successfully completed if the wireless devicereceives the first DCI via the PDCCH in the first CORESET before theresponse window expires. The wireless device may stop the first timer,if configured, if the BFR procedure is successfully completed.

FIG. 17 shows an example of a BFR procedure. In some communicationsystems, a wireless device may stop a BWP inactivity timer if a randomaccess procedure is initiated, and/or the wireless device may restartthe BWP inactivity timer if the random access procedure is successfullycompleted (e.g., based on or in response to receiving DCI addressed to aC-RNTI of the wireless device). At step 1700, a wireless device mayreceive one or more RRC messages comprising BFR parameters. At step1702, the wireless device may detect at least one beam failure accordingto at least one BFR parameter. The wireless device may start a firsttimer, if configured, based on detecting the at least one beam failure.At step 1704, the wireless device may select a beam (e.g., a selectedbeam) based on detecting the at least one beam failure. The selectedbeam may be a beam with good channel quality (e.g., based on RSRP, SINR,and/or BLER) that may be selected from a set of candidate beams. Thecandidate beams may be indicated by a set of reference signals (e.g.,SSBs, or CSI-RSs). At step 1706, the wireless device may send (e.g.,transmit) at least a first BFR signal to a base station, for example,based on selecting the beam (e.g., selected beam). The at least firstBFR signal may be associated with the selected beam. The wireless devicemay send (e.g., transmit) the at least first BFR signal with atransmission beam corresponding to a receiving beam associated with theselected beam. The at least first BFR signal may be a preamble sent(e.g., transmitted) via a PRACH resource, an SR signal sent (e.g.,transmitted) via a PUCCH resource, a beam failure recovery signal sent(e.g., transmitted) via a PUCCH resource, and/or a beam report sent(e.g., transmitted) via a PUCCH and/or PUSCH resource. At step 1708, thewireless device may start a response window, for example, based onsending (e.g., transmitting) the at least first BFR signal. The responsewindow may be associated with a timer with a value configured by thebase station. The wireless device may monitor a PDCCH in a firstCORESET, for example, if the response window is running. The firstCORESET may be configured by the BFR parameters (e.g., RRC). The firstCORESET may be associated with the BFR procedure. The wireless devicemay monitor the PDCCH in the first CORESET in condition of transmittingthe at least first BFR signal.

At step 1710, the wireless device may detect (e.g., receive) a first DCIvia the PDCCH in the first CORESET, for example, if the response windowis running. At step 1712, the wireless device may determine that the BFRprocedure has successfully completed, for example, if the wirelessdevice receives the first DCI via the PDCCH in the first CORESET beforethe response window expires. The wireless device may stop the firsttimer, if configured, based on the BFR procedure successfully beingcompleted. The wireless device may stop the response window, forexample, based on the BFR procedure successfully being completed. If theresponse window expires, and the wireless device does not receive theDCI (e.g., at step 1710), the wireless device may, at step 1714,increment a transmission number. The transmission number may beinitialized to a first number (e.g., 0) before the BFR procedure istriggered. At step 1714, if the transmission number indicates a numberless than the configured maximum transmission number, the wirelessdevice may repeat one or more actions (e.g., at step 1704). The one ormore actions to be repeated may comprise at least one of a BFR signaltransmission, starting the response window, monitoring the PDCCH, and/orincrementing the transmission number, for example, if no responsereceived during the response window is running. At step 1716, if thetransmission number indicates a number equal or greater than theconfigured maximum transmission number, the wireless device may declarethe BFR procedure is unsuccessfully completed.

A wireless device (e.g., a MAC entity of the wireless device) may beconfigured by an RRC message, for example, for a beam failure recoveryprocedure. The beam failure recovery procedure may be used forindicating to a serving base station of a new (e.g., candidate)synchronization signal block (SSB) and/or CSI-RS, for example, if a beamfailure is detected. The beam failure may be detected on one or moreserving SSB(s) and/or CSI-RS(s) of the serving base station. The beamfailure may be detected by counting a beam failure instance indicationfrom a lower layer of the wireless device (e.g., PHY layer) to the MACentity.

An RRC message may configure a wireless device with one or moreparameters (e.g., in BeamFailureRecoveryConfig) for a beam failuredetection and recovery procedure. The one or more parameters maycomprise one or more of: beamFailureInstanceMaxCount for a beam failuredetection, beamFailureDetectionTimer for the beam failure detection,beamFailureRecoveryTimer for a beam failure recovery procedure,rsrp-ThresholdSSB, an RSRP threshold for a beam failure recovery,PowerRampingStep for the beam failure recovery,preambleReceivedTargetPower for the beam failure recovery, preambleTxMaxfor the beam failure recovery, and/or ra-ResponseWindow. Thera-ResponseWindow may be a time window to monitor one or more responsesfor the beam failure recovery using a contention-free RA preamble.

FIG. 18 shows an example of beam failure instance (BFI) indication. Awireless device may use at least one wireless device variable for a beamfailure detection. A BFI counter (e.g., BFI_COUNTER) may be one of theat least one wireless device variable. The BFI counter may be a counterfor a beam failure instance indication. The BFI counter may be initiallyset to zero before time T 1800. The wireless device may start, orrestart, a beam failure detection timer (e.g.,beamFailureDetectionTimer) at time T 1800 and/or increment the BFIcounter, for example, based on a wireless device (e.g., a MAC entity ofthe wireless device) receiving a beam failure instance indication from alower layer (e.g., PHY) of the wireless device. The wireless device mayincrement the BFI counter, for example, in addition to starting orrestarting the beam failure detection timer (e.g., BFR timer in FIG. 18at time T 1800, 2T 1802, 4T 1806, 5T 1808, 6T 1810, etc.). The wirelessdevice may initiate a random access procedure such as for a beam failurerecovery (e.g., on an SpCell, and/or if the active UL BWP is configuredwith BeamFailureRecoveryConfig) based on the BFI counter being greaterthan or equal to a value such as beamFailureInstanceMaxCount (e.g., attime T 1800, 2T 1802, 5T 1808 in FIG. 18). The wireless device may starta beam failure recovery timer (e.g., beamFailureRecoveryTimer, ifconfigured), for example, based on the active UL BWP being configuredwith a beam failure recovery configuration (e.g.,BeamFailureRecoveryConfig). The wireless device may start the beamfailure recovery timer, for example, based on or in response to a BFIcounter (e.g., BFI_COUNTER) being equal to or greater than a value suchas beamFailureInstanceMaxCount. The wireless device may use the one ormore parameters in the beam failure recover configuration (e.g.,powerRampingStep, preambleReceivedTargetPower, and/or preambleTransMax),for example, based on or in response to the initiating the random accessprocedure. The wireless device may set the BFI counter to zero, forexample, based on the beam failure detection timer expiring. Thewireless device may determine that the beam failure recovery procedurehas successfully completed, for example, based on the random accessprocedure being successfully completed. The random access procedure maybe a contention-free random access procedure.

A wireless device may initiate a random access procedure (e.g., on anSpCell) for a beam failure recovery if, for example, the active UL BWPis not configured with BeamFailure RecoveryConfig. A wireless device mayinitiate a random access procedure (e.g., on an SpCell) for abeamfailure recovery, for example, based on, or in response to, a BFIcounter (e.g., BFI_COUNTER) being greater than or equal to a value, suchas beamFailureInstanceMaxCount. The random access procedure may be acontention-based random access procedure.

A wireless device may initiate a random access procedure at time 6T1810, for example, a based on a first value (e.g., 3 or any other value)being reached. The wireless device may set the BFI counter to zero(e.g., in FIG. 18, between time 3T 1804 and 4T 1806), for example, basedon the beam failure detection timer (e.g., beamFailureDetectionTimer)expiring. The wireless device may set the BFI_Counter to zero, forexample, if the beamFailureDetectionTimer, the BFI_Counter, and/or anyof the reference signals used for beam failure detection (e.g.,RadioLinkMonitoring RS) are reconfigured by a higher layer (e.g., RRC).The wireless device may determine that the beam failure recoveryprocedure has successfully completed, for example, based on the randomaccess procedure (e.g., a contention-free random access or acontention-based random access) being successfully completed. Thewireless device may stop the beam failure recovery timer (e.g.,beamFailureRecoveryTimer) (if configured), for example, based on therandom access procedure (e.g., a contention-free random access) issuccessfully completed. The wireless device may reset the BFI_COUNTER tozero, for example, if the random access procedure (e.g., contention-freerandom access) is successfully completed.

A MAC entity may start ra-ResponseWindow at a first PDCCH occasion fromthe end of the transmitting the contention-free random access preamble,for example, if a MAC entity of a wireless device sends (e.g.,transmits) a contention-free random access preamble for a BFR procedure.The ra-ResponseWindow may be configured in BeamFailureRecoveryConfig.The wireless device may monitor at least one PDCCH (e.g., of an SpCell)for a response to the beam failure recovery request, for example, if thera-ResponseWindow is running. The beam failure recovery request may beidentified and/or indicated by a C-RNTI. The wireless device maydetermine that a random access procedure has successfully completed, forexample, if a MAC entity of a wireless device receives, from a lowerlayer of the wireless device, a notification of a reception of at leastone PDCCH transmission, and if the at least one PDCCH transmission isaddressed to a C-RNTI, and/or if a contention-free random accesspreamble for a beam failure recovery request is transmitted by the MACentity.

A wireless device may initiate a contention-based random access preamblefor a beam failure recovery request. The wireless device (e.g., a MACentity of the wireless device) may start ra-ContentionResolutionTimer,for example, if the wireless device transmits Msg3. Thera-ContentionResolutionTimer may be configured by RRC. Based on thestarting the ra-ContentionResolutionTimer, the wireless device maymonitor at least one PDCCH if the ra-ContentionResolutionTimer isrunning. The wireless device may consider the random access proceduresuccessfully completed, for example, if the wireless device (e.g., MACentity) receives, from a lower layer of the wireless device, anotification of a reception of the at least one PDCCH transmission, if aC-RNTI MAC-CE is included in the Msg3, if a random access procedure isinitiated for a beam failure recovery, and/or the at least one PDCCHtransmission is addressed to a C-RNTI of the wireless device. Thewireless device may stop the ra-ContentionResolutionTimer, for example,based on the random access procedure being successfully completed. Thewireless device may determine that the beam failure recovery hassuccessfully completed, for example, if a random access procedure of abeam failure recovery is successfully completed.

A wireless device may be configured (e.g., for a serving cell) with afirst set of periodic CSI-RS resource configuration indexes by a higherlayer parameter (e.g., Beam-Failure-Detection-RS-ResourceConfig,failureDetectionResources, etc.). The wireless device may be configuredwith a second set of CSI-RS resource configuration indexes and/orSS/PBCH block indexes by a higher layer parameter (e.g.,Candidate-Beam-RS-List, candidateBeamRSList, etc.). The first set ofCSI-RS resource configuration indexes and/or SS/PBCH block indexesand/or the second set of CSI-RS resource configuration indexes and/orSS/PBCH block indexes may be used for radio link quality measurements onthe serving cell. The wireless device may determine a first set toinclude SS/PBCH block indexes and periodic CSI-RS resource configurationindexes, for example, if a wireless device is not provided with a higherlayer parameter (e.g., Beam-Failure-Detection-RS-ResourceConfig). TheSS/PBCH block indexes and the periodic CSI-RS resource configurationindexes may comprise the same values as one or more RS indexes in one ormore RS sets. The one or more RS indexes in the one or more RS sets maybe indicated by one or more TCI-states (e.g., via a higher layerparameter TCI-states). The one or more TCI-states may be used forrespective control resource sets for which the wireless device may beconfigured to monitor a PDCCH. The wireless device may monitor (e.g.,expect) a first set to include up to two RS indexes. If there are two RSindexes in a TCI state, the first set may include one or more RS indexeswith QCL-TypeD configuration for the TCI state. The wireless device maymonitor (e.g., expect) a single port RS in the first set.

A wireless device may expect a first set of periodic CSI-RS resourceconfigurations to include, for example, up to two RS indexes. The firstset of periodic CSI-RS resource configurations may include one or moreRS indexes with QCL-TypeD configuration, for example, based on the firstset of periodic CSI-RS resource configurations includes two RS indexes.A wireless device may expect a single port RS in the first set ofperiodic CSI-RS resource configurations. A first threshold (e.g.,Qout,LR) may correspond to a first default value of a first higher layerparameter (e.g., RLM-IS-OOS-thresholdConfig,rlmInSyncOutOfSyncThreshold, etc.). A second threshold (e.g., Qin,LR)may correspond to a second default value of a higher layer parameter(e.g., Beam-failure-candidate-beam-threshold, rsrp-ThresholdSSB, etc.).A physical layer in the wireless device may compare a first radio linkquality according to the first set with the first threshold. For thefirst set, the wireless device may assess the first radio link qualitybased on periodic CSI-RS resource configurations or SS/PBCH blocks. Theperiodic CSI-RS resource configurations and/or the SS/PBCH blocks may beassociated (e.g., quasi co-located) with at least one DM-RS of a PDCCHmessage that may be monitored by the wireless device. The wirelessdevice may apply the second threshold to a first L1-RSRP measurementthat may be obtained from one or more SS/PBCH blocks. The wirelessdevice may apply the second threshold to a second L1-RSRP measurementthat may be obtained from one or more periodic CSI-RS resources, forexample, after scaling a respective CSI-RS reception power with a valueprovided by a higher layer parameter (e.g., Pc_SS, powerControlOffsetSS,etc.).

A wireless device may assess the first radio link quality of the firstset. A physical layer in the wireless device may provide an indicationto higher layers (e.g., MAC), for example, if the first radio linkquality for all corresponding resource configurations in the first setis less than the first threshold. The wireless device may use thecorresponding resource configurations in the first set to assess thefirst radio link quality. The physical layer may inform the higherlayers (e.g., MAC, RRC), for example, if the first radio link quality isless than the first threshold with a first periodicity. The firstperiodicity may be determined by the maximum of the shortest periodicityamong periodic CSI-RS configurations or SS/PBCH blocks in the first setand a time value (e.g., 2 ms or any other duration). The wireless devicemay access the periodic CSI-RS configurations or the SS/PBCH blocks forthe first radio link quality. Based on a request from higher layers(e.g., MAC layer), a wireless device may provide to higher layers theperiodic CSI-RS configuration indexes and/or the SS/PBCH block indexesfrom the second set, and corresponding L1-RSRP measurements that may begreater than or equal to the second threshold.

A wireless device may be configured with one CORESET, for example, by ahigher layer parameter (e.g., Beam-failure-Recovery-Response-CORESET)and/or via a link to a search space set. The wireless device may beconfigured with an associated search space that may be provided by ahigher layer parameter (e.g., search-space-config,recoverySearchSpaceId, etc.). The search space may be used formonitoring a PDCCH in the control resource set. The wireless device maynot expect to be provided with a second search space set for monitoringa PDCCH in the CORESET, for example, if the wireless device is providedby a higher layer parameter (e.g., recoverySearchSpaceId). The CORESETmay be associated with the search space set provided by a higher layerparameter (e.g., recoverySearchSpaceId). The wireless device may receivefrom higher layers (e.g., MAC layer), by a parameter (e.g.,PRACH-ResourceDedicatedBFR), a configuration for a PRACH transmission.The wireless device may monitor the PDCCH in a search space set (e.g.,which may be provided by a higher layer parameter such asrecoverySearchSpaceId) for detection of a DCI format starting from aslot (e.g., slot n+4) within a window, for example: for the PRACHtransmission in slot n; based on antenna port quasi co-locationparameters associated with periodic CSI-RS resource configuration;and/or with SS/PBCH block associated with a first RS index provided bythe higher layers. The window may be configured by a higher layerparameter (e.g., Beam-failure-recovery-request-window,BeamFailureRecoveryConfig, etc.). The DCI format may be CRC scrambled bya C-RNTI or MCS-C-RNTI. The first RS index may be provided by the higherlayers. For a PDCCH monitoring and for a corresponding PDSCH reception,the wireless device may use the same antenna port quasi-collocationparameters as the ones associated with the first RS index (e.g., as formonitoring the PDCCH), for example, at least until the wireless devicereceives (e.g., by higher layers) an activation for a TCI state or anyof the parameters (e.g., TCI-StatesPDCCH, ToAddlist,TCI-StatesPDCCH-ToReleaseList).

A wireless device may monitor or continue to monitor downlink and/orcontrol channel resources (e.g., PDCCH) candidates in a search spaceset. The wireless device may monitor the downlink and/or control channelresources (e.g., PDCCH) candidates in the search space set, for example,at least until the wireless device receives a MAC-CE activation command(e.g., wireless device-specific PDCCH MAC CE) for a TCI state and/or ahigher layer parameter (e.g., TCI-StatesPDCCH-ToAddlist and/orTCI-StatesPDCCH-ToReleaseList), for example, after the wireless devicedetects the DCI format with CRC scrambled by the C-RNTI or MCS-CRNTI inthe search space set (e.g., which may be by the higher layer parameterrecoverySearchSpaceId). The wireless device may not initiate acontention-free random access procedure for a beam failure recovery, forexample, based on the wireless device not being provided with a higherlayer parameter (e.g., recoverySearchSpaceId). A wireless device mayinitiate a contention-based random access procedure for a beam failurerecovery, for example, based on or in response to not being providedwith the higher layer parameter (e.g., recoverySearchSpaceId).

A wireless device may be configured with a set of resource indexes forradio link monitoring by a higher layer parameter (e.g.,failureDetectionResources) for each DL BWP of a SpCell via acorresponding set of higher layer parameters (e.g.,RadioLinkMonitoringRS). The wireless device may be provided with ahigher layer parameter, such as CSI-RS resource configuration index(e.g., csi-RS-Index) or a SS/PBCH block index (e.g., ssb-Index). Thewireless device may use a first RS provided by the higher layerparameter TCI-states for PDCCH receptions, for example, if: i) thehigher layer parameter TCI-states for PDCCH receptions comprises onlyone RS (e.g., the first RS), ii) wireless device is not provided higherlayer parameter RadioLinkMonitoringRS, and/or iii) the wireless deviceis provided higher layer parameter TCI-states for PDCCH receptions. Thewireless device may use a first RS provided by the higher layerparameter TCI-states for PDCCH receptions, for example, if: i) thewireless device is not provided higher layer parameterRadioLinkMonitoringRS, ii) the wireless device is provided higher layerparameter TCI-states for PDCCH receptions, and/or iii) the higher layerparameter TCI-states comprise two RSs. The first RS may have QCL-TypeD.The wireless device may use the first RS for radio link monitoring inresponse to the first RS having QCL-TypeD. The two RSs may not haveQCL-TypeD simultaneously. The wireless device may not use an aperiodicor semi-persistent RS for radio link monitoring, for example, if: i) thewireless device is not provided higher layer parameterRadioLinkMonitoringRS and/or ii) the wireless device is provided higherlayer parameter TCI-states for PDCCH receptions.

A base station may configure a wireless device with UL BWPs and DL BWPs,for example, to enable bandwidth adaptation (BA) for a PCell. The basestation may configure the wireless device with at least DL BWP(s) (e.g.,an SCell may not have UL BWPS) to enable BA for an SCell, for example,if CA is configured. For the PCell, a first initial BWP may be a firstBWP used for initial access. For the SCell, a second initial BWP may bea second BWP configured for the wireless device to first operate on theSCell if the SCell is activated.

A wireless device may switch a first (e.g., active) DL BWP and a first(e.g., active) UL BWP independently, for example, in paired spectrum(e.g., FDD). A wireless device may switch a second (e.g., active) DL BWPand a second (e.g., active) UL BWP simultaneously, for example, inunpaired spectrum (e.g., TDD). Switching between configured BWPs may bebased on DCI and/or an inactivity timer. An expiry of the inactivitytimer associated with a cell may switch an active BWP to a default BWP,for example, if the inactivity timer is configured for a serving cell.The default BWP may be configured by the network.

One UL BWP for each uplink carrier and one DL BWP may be active at atime in an active serving cell, for example, in FDD systems configuredwith BA. One DL/UL BWP pair may be active at a time in an active servingcell, for example, in TDD systems. Operating on the one UL BWP and theone DL BWP (and/or the one DL/UL pair) may enable a wireless device touse a reasonable amount of power (e.g., reasonable battery consumption).BWPs other than the one UL BWP and the one DL BWP that the wirelessdevice may be configured with may be deactivated. The wireless devicemay refrain from monitoring a PDCCH, and/or may refrain fromtransmitting via a PUCCH, PRACH, and/or UL-SCH, for example, ondeactivated BWPs.

A serving cell may be configured with a first quantity (e.g., four orany other value) of BWPs. A wireless device and/or a base station mayhave an active BWP (e.g., one active BWP) at any point in time, forexample, for an activated serving cell (e.g., PCell, SCell). A BWPswitching for a serving cell may be used to activate an inactive BWPand/or deactivate an active BWP. The BWP switching may be controlled bya PDCCH indicating a downlink assignment or an uplink grant. The BWPswitching may be controlled by an inactivity timer (e.g.,bwpInactivityTimer). The BWP switching may be controlled by an RRCsignaling. The BWP switching may be controlled by a wireless device(e.g., a MAC entity), for example, based on initiating a random accessprocedure. A DL BWP (e.g., indicated by first ActiveDownlinkBWP-ID whichmay be included in RRC signaling) and/or an UL BWP (e.g., indicated byfirstActiveDuplinkBWP-ID which may be included in RRC signaling) may beinitially active without receiving a PDCCH indicating a downlinkassignment or an uplink grant, for example, based on an addition of anSpCell or an activation of an SCell. The active BWP for a serving cellmay be indicated by an RRC message and/or a PDCCH message (e.g., PDCCHorder). A DL BWP may be paired with an UL BWP, and/or BWP switching maybe common for both UL and DL, for example, for unpaired spectrum (e.g.,TDD).

An activated serving cell (e.g. a MAC entity of the activated servingcell) 1 (e.g., PCell, SCell) may be configured with one or more BWPsand/or may be configured based on the BWP being activated. The activatedserving cell (e.g., the MAC entity of the activated serving cell) mayperform at least one of: transmitting via an UL-SCH using the one ormore BWPs; transmitting via a RACH using the one or more BWPs if PRACHoccasions are configured; monitoring a PDCCH using the one or more BWPs;transmitting an SRS using the one or more BWPs, if configured;transmitting via a PUCCH using the one or more BWPs, if configured;reporting CSI for the one or more BWPs; receiving via a DL-SCH using theone or more BWPs; initializing or reinitializing any suspendedconfigured uplink grants of configured grant Type 1 using the one ormore BWPs (e.g., based on a stored configuration, if any); and/orstarting in a symbol (e.g., based on a procedure).

A wireless device (e.g., a MAC entity of a wireless device), for anactivated serving cell (e.g., PCell, SCell) configured with one or moreBWPs and/or based on the BWP being deactivated, may not transmit via aUL-SCH using the one or more BWPs; may not transmit via a RACH using theone or more BWPs; may not monitor a PDCCH using the one or more BWPs;may not report CSI for the one or more BWPs; may not transmit via aPUCCH using the one or more BWPs; may not transmit an SRS using the oneor more BWPs, may not receive via a DL-SCH using the one or more BWPs;may clear any configured downlink assignment and configured uplink grantof configured grant Type 2 using the one or more BWPs; and/or maysuspend any configured uplink grant of configured Type 1 using the oneor more BWPs (e.g., inactive BWPs).

A base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may initiate a random access procedure(e.g., contention-based random access, contention-free random access) ona serving cell, for example, based on PRACH occasions being configuredfor an active UL BWP, of the serving cell, with an uplink BWP ID; theserving cell being an SpCell; and/or a downlink BWP ID of an active DLBWP of the serving cell not being the same as the uplink BWP ID. Thebase station and/or the wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may switch from the active DL BWP to aDL BWP with a second downlink BWP ID same as the uplink BWP ID, forexample, based on the prior initiation. The base station and/or thewireless device (e.g., a MAC entity of a base station and/or a wirelessdevice) may perform the random access procedure on the DL BWP of theserving cell (e.g., SpCell) and the active UL BWP of the serving cell,for example, based on or in response to the switching.

A base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may initiate a random access procedure(e.g., contention-based random access, contention-free random access) ona serving cell (e.g., SCell), for example, based on PRACH occasionsbeing configured for an active UL BWP of the serving cell; and/or theserving cell not being an SpCell. The base station and/or the wirelessdevice (e.g., a MAC entity of a base station and/or a wireless device)may perform the random access procedure on an active DL BWP of an SpCelland an active UL BWP of the serving cell, for example, based on theinitiation.

A base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may initiate a random access procedureon a serving cell, for example, based on

PRACH resources not being configured for an active UL BWP of the servingcell. The MAC entity may switch the active UL BWP to an uplink BWP(initial uplink BWP), for example, based on the initiation. The uplinkBWP may be indicated by RRC signaling (e.g., initialULBWP). The basestation and/or the wireless device (e.g., a MAC entity of a base stationand/or a wireless device) may switch an active DL BWP to a downlink BWP(e.g., initial downlink BWP), for example, based on the serving cellbeing an SpCell. The downlink BWP may be indicated by RRC signaling(e.g., initialDLBWP). The base station and/or the wireless device (e.g.,a MAC entity of a base station and/or a wireless device) may perform therandom access procedure on the uplink BWP and the downlink BWP, forexample, based on or in response to the switching.

A base station and/or a wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may initiate a random access procedureon a serving cell, for example, based on PRACH resources not beingconfigured for an active UL BWP of the serving cell (e.g., SCell). Thebase station and/or the wireless device (e.g., a MAC entity of a basestation and/or a wireless device) may switch the active UL BWP to anuplink BWP (initial uplink BWP), for example, based on the initiation.The uplink BWP may be indicated by RRC signaling (e.g., initialULBWP).The base station and/or the wireless device (e.g., a MAC entity of abase station and/or a wireless device) may perform the random accessprocedure on the uplink BWP and an active downlink BWP of an SpCell, forexample, based on the serving cell is not an SpCell.

A wireless device may perform BWP switching to a BWP indicated by aPDCCH message, for example, if a base station and/or a wireless device(e.g., a MAC entity of a base station and/or a wireless device) receivesa PDCCH message (e.g., a PDCCH order) for a BWP switching for a servingcell. The wireless device may receive the PDCCH message for the BWPswitching, for example, if a random access procedure associated withthis serving cell is not ongoing. A wireless device may determinewhether to switch a BWP or ignore the PDCCH message for the BWPswitching, for example, if a base station and/or a wireless device(e.g., a MAC entity of a base station and/or a wireless device) receiveda PDCCH message for a BWP switching for a serving cell while a randomaccess procedure is ongoing in the MAC entity. The wireless device mayperform the BWP switching to a new BWP indicated by the PDCCH message.The base station and/or the wireless device (e.g., a MAC entity of abase station and/or a wireless device) may stop the ongoing randomaccess procedure and/or initiate a second random access procedure afterperforming BWP switching, for example, if the wireless device (e.g., aMAC entity of the wireless device) decides to perform BWP switching tothe new BWP (e.g., which may be indicated by the PDCCH message). Thewireless device (e.g., the MAC entity for the wireless device) maydecide to perform BWP switching, for example, based on or in response toreceiving a PDCCH message (e.g., other than successful contentionresolution) or the RRC configuration. The base station and/or thewireless device (e.g., a MAC entity of a base station and/or a wirelessdevice) may continue with the ongoing random access procedure on theserving cell, for example, if the MAC decides to ignore the PDCCHmessage for the BWP switching.

The base station and/or the wireless device (e.g., a MAC entity of abase station and/or a wireless device) may start, or restart, a BWPinactivity timer associated with the active DL BWP for one or morereasons. The MAC entity may start, or restart, a BWP inactivity timer(e.g., BWP-InactivityTimer) associated with the active DL BWP, forexample, if one or more of the following occur: an activated servingcell configured with a BWP inactivity timer is configured (e.g., via RRCsignaling including defaultDownlinkBWP parameter); if a Default-DL-BWPis configured and an active DL BWP is not a BWP indicated by theDefault-DL-BWP; and/or if the Default-DL-BWP is not configured and theactive DL BWP is not the initial DL BWP (e.g., via RRC signalingincluding initialDownlinkBWPparameter). The MAC may start, or restart, aBWP inactivity timer (e.g., BWP-InactivityTimer) associated with theactive DL BWP, for example, if one or more of the following occur: if aPDCCH message addressed to C-RNTI or CS-RNTI indicating downlinkassignment or uplink grant is received on or for the active BWP, and/orif there is not an ongoing random access procedure associated with theactivated serving cell.

The base station and/or the wireless device (e.g., a MAC entity of abase station and/or a wireless device) may start or restart the BWPinactivity timer (e.g., BWP-InactivityTimer) associated with the activeDL BWP, for example, if one or more of the following occur: if aBWP-InactivityTimer is configured for an activated serving cell, if aDefault-DL-BWP is configured and an active DL BWP is not a BWP indicatedby the Default-DL-BWP, and/or if the Default-DL-BWP is not configuredand an active DL BWP is not the initial DL BWP. The base station and/orthe wireless device (e.g., a MAC entity of a base station and/or awireless device) may start or restart the BWP inactivity timer (e.g.,BWP-InactivityTimer) associated with the active DL BWP, for example, ifone or more of the following occur: if a MAC-PDU is transmitted in aconfigured uplink grant or received in a configured downlink assignment,and/or if there is not an ongoing random access procedure associatedwith the activated serving cell.

The base station and/or the wireless device (e.g., a MAC entity of abase station and/or a wireless device) may start or restart the BWPinactivity timer (e.g., BWP-InactivityTimer) associated with the activeDL BWP, for example, if one or more of the following occur: if aBWP-InactivityTimer is configured for an activated serving cell, if aDefault-DL-BWP is configured and an active DL BWP is not a BWP indicatedby the Default-DL-BWP, and/or if the Default-DL-BWP is not configuredand the active DL BWP is not the initial DL BWP. The base station and/orthe wireless device (e.g., a MAC entity of a base station and/or awireless device) may start or restart the BWP inactivity timer (e.g.,BWP-InactivityTimer) associated with the active DL BWP, for example, ifone or more of the following occur: if a PDCCH message addressed toC-RNTI or CS-RNTI indicating downlink assignment or uplink grant isreceived on or for the active BWP, if a MAC-PDU is transmitted in aconfigured uplink grant or received in a configured downlink assignment,and/or if an ongoing random access procedure associated with theactivated Serving Cell is successfully completed in response toreceiving a PDCCH message addressed to a C-RNTI.

The base station and/or the wireless device (e.g., a MAC entity of abase station and/or a wireless device) may start or restart the BWPinactivity timer (e.g., BWP-InactivityTimer) associated with the activeDL BWP based on switching the active BWP. For example, the MAC entitymay start or restart the BWP-InactivityTimer associated with the activeDL BWP if a PDCCH message for BWP switching is received and the wirelessdevice switches an active DL BWP to the DL BWP, and/or if one or more ofthe following occur: if a default downlink BWP is configured and the DLBWP is not the default downlink BWP, and/or if a default downlink BWP isnot configured and the DL BWP is not the initial downlink BWP.

The base station and/or the wireless device (e.g., a MAC entity of abase station and/or a wireless device) may stop the BWP inactivity timer(e.g., BWP-InactivityTimer) associated with an active DL BWP of theactivated serving cell, for example, if one or more of the followingoccur: if BWP-InactivityTimer is configured for an activated servingcell, if the Default-DL-BWP is configured and the active DL BWP is notthe BWP indicated by the Default-DL-BWP, and/or if the Default-DL-BWP isnot configured and the active DL BWP is not the initial BWP; and/or if arandom access procedure is initiated on the activated serving cell. TheMAC entity may stop a second BWP inactivity timer (e.g.,BWP-InactivityTimer) associated with a second active DL BWP of anSpCell, for example, if the activated Serving Cell is an SCell (otherthan a PSCell).

The base station and/or the wireless device (e.g., a MAC entity of abase station and/or a wireless device) may perform BWP switching to aBWP indicated by the Default-DL-BWP, for example, if one or more of thefollowing occur: if a BWP inactivity timer (e.g., BWP-InactivityTimer)is configured for an activated serving cell, if the Default-DL-BWP isconfigured and the active DL BWP is not the BWP indicated by theDefault-DL-BWP, if the Default-DL-BWP is not configured and the activeDL BWP is not the initial BWP, if BWP-InactivityTimer associated withthe active DL BWP expires, and/or if the Default-DL-BWP is configured.The MAC entity may perform BWP switching to the initial DL BWP, forexample, if the MAC entity may refrain from performing BWP switching toa BWP indicated by the Default-DL-BWP.

A wireless device may be configured for operation in BWPs of a servingcell. The wireless device may be configured (e.g., by higher layers) forthe serving cell for a set of (e.g., four) bandwidth parts (BWPs) forreceptions by the wireless device (e.g., DL BWP set) in a DL bandwidthby a parameter (e.g., DL-BWP). The wireless device may be configuredwith a set of (e.g., four or any other quantity) BWPs for transmissionsby the wireless device (e.g., UL BWP set) in an UL bandwidth by aparameter (e.g., UL-BWP) for the serving cell. A wireless device may notreceive (e.g., be provided) higher layer parameter initialDownlinkBWP.If the initialDownlink BWP has not been received (e.g., provided), awireless device may determine an initial active DL BWP, for example, by:a location and number of contiguous PRBs; a subcarrier spacing; and/or acyclic prefix (e.g., for PDCCH reception in the control resource set fora Type0-PDCCH common search space). The contiguous PRBs may start from aPRB having a lowest index and may end at a PRB with a highest indexamong PRBs of a control resource set for Type0-PDCCH common searchspace. A wireless device may be provided a higher layer parameter (e.g.,initialDownlinkBWP). An initial active DL BWP may be a BWP indicated bythe higher layer parameter (e.g., initialDownlinkBWP), for example,after or in response to being provided the higher layer parameter (e.g.,initialDownlinkBWP). A wireless device may be provided (e.g., by ahigher layer) a parameter (e.g., initial-UL-BWP) for an initial activeUL BWP for a random access procedure, for example, for operation on aprimary cell or on a secondary cell. The wireless device may be providedwith an initial active UL BWP (e.g., by a higher layer) parameter (e.g.,Active-BWP-DL-Pcell, initialUplinkBWP, etc.) for first active DL BWP forreceptions, for example, if a wireless device has a dedicated BWPconfiguration. The wireless device may be provided with an initialuplink BWP on a supplementary carrier by a second higher layer parameter(e.g., initialUplinkBWP in a supplementary uplink), for example, if thewireless device is configured with a supplementary carrier. The wirelessdevice may be provided (e.g., by a higher layer) a parameter (e.g.,Active-BWP-UL-Pcell, firstActiveDownlinkBWP-Id, etc.) for a first activeUL BWP for transmissions on a primary cell, for example, if a wirelessdevice has a dedicated BWP configuration. The higher layer parameter mayindicate a first active DL BWP for receptions. The wireless device maybe provided by a second higher layer parameter (e.g.,firstActiveUplinkBWP-Id), for example, if the wireless device has adedicated BWP configuration. The higher layer parameter may indicate afirst active UL BWP for transmissions on the primary cell.

For a DL BWP and/or an UL BWP in a first set of DL BWPs or a second setof UL BWPs, respectively, the wireless device may be provided at leastone of the following parameters for a serving cell: a subcarrier spacingby higher layer parameter subcarrierSpacing or UL-BWP-mu; a cyclicprefix by higher layer parameter cyclicPrefix; an index in the first setof DL BWPs or in the second set of UL BWPs by respective higher layerparameters bwp-Id (e.g., DL-BWP-ID, UL-BWP-ID); a third set ofBWP-common and a fourth set of BWP-dedicated parameters by a higherlayer parameter bwp-Common and a higher layer parameter bwp-Dedicated,respectively.

A DL BWP from a first set of configured DL BWPs (e.g., associated with aDL BWP index provided by higher layer parameter such as bwp-ID) may bepaired and/or linked with an UL BWP from a second set of configured ULBWPs (e.g., associated with an UL BWP index provided by higher layerparameter such as bwp-ID). A DL BWP from a first set of configured DLBWPs may be paired with an UL BWP from a first set of configured ULBWPs, for example, if the DL BWP index and the UL BWP index are equal(e.g., for unpaired spectrum operation). A wireless device may notexpect to receive a configuration in which the center frequency for a DLBWP is different from the center frequency for an UL BWP, for example,if the DL-BWP-index of the DL BWP is equal to the UL-BWP-index of the ULBWP (e.g., for unpaired spectrum operation).

A wireless device may be configured with CORESETs for every type ofcommon search space and/or for a wireless device-specific search space,for example, for a DL BWP in a first set of DL BWPs on a primary cell.The wireless device may not expect to be configured without a commonsearch space on the PCell, and/or on the PSCell, of the MCG in the DLBWP (e.g., active DL BWP). The wireless device may be configured withcontrol resource sets for PUCCH transmissions, for example, for an ULBWP in a second set of UL BWPs of the PCell or of the PUCCH-SCell. Awireless device may receive a PDCCH message and/or a PDSCH message in aDL BWP, for example, according to a configured subcarrier spacing and/ora CP length for the DL BWP. A wireless device may transmit, via a PUCCHand/or via a PUSCH, in an UL BWP, for example, according to a configuredsubcarrier spacing and CP length for the UL BWP.

A BWP indicator field value may indicate an active DL BWP, from thefirst set of configured DL BWPs, for DL receptions, for example, if theBWP indicator field is configured in DCI format 1_1. The BWP indicatorfield value may indicate an active UL BWP, from the second set ofconfigured UL BWPs, for UL transmissions.

The wireless device may set the active UL BWP to the UL BWP indicated bythe bandwidth part indicator field in the DCI format 0_1, for example,based on a bandwidth part indicator field being configured in DCI format0_1 and/or the bandwidth part indicator field value indicating an UL BWPdifferent from an active UL BWP. The wireless device may set the activeDL BWP to the DL BWP indicated by the bandwidth part indicator field inthe DCI format 1_1, for example, based on a bandwidth part indicatorfield being configured in DCI format 1_1 and/or the bandwidth partindicator field value indicating a DL BWP different from an active DLBWP.

A wireless device may be provided (e.g., for the primary cell) with ahigher layer parameter (e.g., Default-DL-BWP, defaultDownlinkBWP-Id, orany other a default DL BWP among the configured DL BWPs), for example,if a BWP indicator field is configured in DCI format 0_1. The higherlayer parameter may indicate a default DL BWP among configured DL BWPs.The default BWP may be the initial active DL BWP, for example, if awireless device is not provided a default DL BWP by a higher layerparameter (e.g., Default-DL-BWP, defaultDownlinkBWP-Id, etc.). Awireless device may detect a DCI format 0_1 indicating active UL BWPchange, or a DCI format 1_1 indicating active DL BWP change, forexample, if a corresponding PDCCH message is received within first threesymbols of a slot.

The wireless device procedures on the secondary cell may be same as on aprimary cell. The wireless device procedures on the secondary cell maybe the same as on a primary cell, for example, based on the wirelessdevice being configured for a secondary cell with higher layer parameter(e.g., defaultDownlinkBWP-Id) indicating a default DL BWP among theconfigured DL BWPs and/or the wireless device being configured withhigher layer parameter bwp-inactivity timer indicating a timer value. Anoperation of the timer value for the secondary cell and the default DLBWP for the secondary cell may be similar to or the same as operationsusing a timer value for the primary cell and a default DL BWP for theprimary cell.

A wireless device may be provided by a higher layer parameter (e.g.,BWP-InactivityTimer). The higher layer parameter may indicate a timerwith a timer value for a serving cell (e.g., primary cell, secondarycell). The wireless device may increment the timer every interval (e.g.,every interval of 1 millisecond for frequency range 1, every 0.5milliseconds for frequency range 2, or any other interval for any otherfrequency range), for example, based on the timer being configured, thetimer running, and/or the wireless device not detecting a DCI format forPDSCH reception on the serving cell for paired spectrum operation. Thewireless device may decrement the timer every interval (e.g., everyinterval of 1 millisecond for frequency range 1, every 0.5 millisecondsfor frequency range 2, or any other interval for any other frequencyrange), for example, based on the timer being configured, the timerrunning, the wireless device not detecting a first DCI format for PDSCHreception and/or the wireless device not detecting a second DCI formatfor PUSCH transmission on the serving cell for unpaired spectrumoperation during the interval.

A wireless device may change an active DL BWP and/or an active UL BWP(e.g., due to a BWP inactivity timer expiration) for a cell. Thewireless device may not receive or transmit in the cell during a timeduration from the beginning of a subframe for a first frequency range(e.g., frequency range 1), or half of a subframe for a second frequency(e.g., frequency range 2), for example, in order to accommodate a delayin changing the active DL BWP or the active UL BWP. The wireless devicemay not receive or transmit in the cell after the BWP inactivity timerexpires, for example, at least until the beginning of a slot in whichthe wireless device may receive or transmit.

A wireless device may be configured by a higher layer (e.g., aconfiguration including parameter firstActiveDownlinkBWP-Id and/orparameter firstActiveUplinkBWP-Id). The higher layer parameter (e.g.,firstActiveDownlinkBWP-Id) may indicate a first active DL BWP on aserving cell (e.g., secondary cell) and/or on a supplementary carrier.The wireless device may use the first active DL BWP on the serving cellas the respective first active DL BWP. The higher layer parameter (e.g.,firstActiveUplinkBWP-Id) may indicate a first active UL BWP on a servingcell (e.g., secondary cell) and/or on a supplementary carrier. Thewireless device may use the first active UL BWP on the serving cell,and/or on the supplementary carrier, as the respective first active ULBWP.

A wireless device may not monitor (e.g., expect) to transmit a PUCCHwith HARQ-ACK on a PUCCH resource indicated by a DCI format 1_0 or a DCIformat 1_1, for example, based on: paired spectrum operation, thewireless device changing its active UL BWP on a primary cell between atime of a detection of the DCI format 1_0 or the DCI format 1_1, and/ora time of a corresponding PUCCH transmission with HARQ-ACK transmissionon the PUCCH. A wireless device may not monitor PDCCH, for example, ifthe wireless device performs RRM measurements over a bandwidth that isnot within the active DL BWP for the wireless device.

A DL BWP index (ID) may be an identifier for a DL BWP. One or moreparameters in an RRC configuration may use the DL BWP-ID to associatethe one or more parameters with the DL BWP. The DL BWP ID of 0 (e.g., DLBWP ID=0) may be associated with the initial DL BWP. An UL BWP index(ID) may be an identifier for an UL BWP. One or more parameters in anRRC configuration may use the UL BWP-ID to associate the one or moreparameters with the UL BWP. The UL BWP ID of 0 (e.g., UL BWP ID=0) maybe associated with the initial UL BWP.

A higher layer parameter (e.g., firstActiveDownlinkBWP-Id) may indicatean ID of a DL BWP to be activated upon performing the reconfiguration,for example, based on a higher layer parameter (e.g.,firstActiveDownlinkBWP-Id) is configured for an SpCell. A higher layerparameter (e.g., firstActiveDownlinkBWP-Id) may indicate an ID of a DLBWP to be used upon MAC-activation of the SCell, for example, based onthe higher layer parameter (e.g., firstActiveDownlinkBWP-Id) beingconfigured for an SCell. A higher layer parameter (e.g.,firstActiveUplinkBWP-Id) may indicate an ID of an UL BWP to be activatedif performing the reconfiguration, for example, based on the higherlayer parameter (e.g., firstActiveUplinkBWP-Id) being configured for anSpCell. A higher layer parameter (e.g., firstActiveUplinkBWP-Id) mayindicate an ID of an UL BWP to be used if MAC-activation of the SCelloccurs, for example, based on a higher layer parameter (e.g.,firstActiveUplinkBWP-Id) being configured for an SCell.

A wireless device, to execute a reconfiguration with sync, may determine(e.g., assume) an uplink BWP indicated in a higher layer parameter(e.g., firstActiveUplinkBWP-Id) to be an active uplink BWP. A wirelessdevice, to execute a reconfiguration with sync, may determine (e.g.,assume) a downlink BWP indicated in a higher layer parameter (e.g.,firstActiveDownlinkBWP-Id) to be an active downlink BWP.

FIG. 19 shows an example of BWP switching. The BWP switching may be on aPCell. A base station 1902 may send (e.g., transmit) one or moremessages (e.g., one or more RRC messages) 1912 for configuring multipleBWPs (e.g., multiple BWPs comprising a DL BWP 0, a DL BWP 1, a DL BWP 2,a DL BWP 3, an UL BWP 0, an UL BWP 1, an UL BWP 2, and an UL BWP 3 shownin a table 1908). The DL (and/or UL) BWP 0 may be a default BWP. The DL(and/or UL) BWP 1 may be an initial active BWP (e.g., an initial DL BWPor an initial UL BWP). A wireless device 1904 may determine the multipleBWPs configured for the wireless device 1904, for example, based on theone or more messages 1912. The base station 1902 may send DCI 1914 for aDL assignment (e.g., at a time n). The DCI 1914 may be sent via the DLBWP 1 (e.g., an initial DL BWP). The wireless device 1904 may receive apacket via the DL BWP 1 or via another active DL BWP (e.g., at a timen+k), for example, based on the DL assignment. The wireless device 1904may start a BWP inactivity timer (e.g., at the time n+k). The wirelessdevice 1904 may start the BWP inactivity timer, for example, afterreceiving scheduled downlink packets. The base station 1902 may send DCI1914 for an UL grant (e.g., at the time n). The DCI 1914 may be sent viathe DL BWP 1 (e.g., a first DL BWP or an initial DL BWP). The wirelessdevice 1904 may send a packet via an UL BWP 1 (e.g., via a first UL BWPor an initial UL BWP at a time n+k), for example, based on the UL grant.The wireless device 1904 may start a BWP inactivity timer (e.g., at thetime n+k). The wireless device 1904 may start the BWP inactivity timer,for example, after sending scheduled uplink packets.

The base station 1902 may send DCI 1919 for BWP switching (e.g., a BWPswitching from the DL BWP 1 to the DL BWP 2). The DCI 1919 may be sentvia the active DL BWP 1 (e.g., at a time m). The wireless device 1904may receive the DCI 1919, for example, by monitoring a PDCCH on theactive DL BWP 1. The wireless device 1904 may switch the DL BWP 1 to theDL BWP 2 (e.g., at a time m+l), for example, based on the DCI 1916.There may be a delay (e.g., a gap) between the wireless device 1904receiving the DCI 1916 and the wireless device 1904 switching to the DLBWP 2. The wireless device 1904 may start and/or re-start the BWPinactivity timer (e.g., at the time m+l), for example, after the BWPswitching. The BWP inactivity timer may expire (e.g., at a time o), forexample, if the wireless device 1904 does not perform reception ortransmission for a period of time (e.g., a period from the time m+l tothe time o). The wireless device 1904 may switch the DL BWP 2 to the DLBWP 0 (e.g., a default BWP). The fallback to the DL BWP 0 may occur(e.g., at a time o+q), for example, after the BWP inactivity timerexpires. There may be a delay (e.g., a gap) between the BWP inactivitytimer expiration (e.g., at a time o) and the wireless device 1904switching to the DL BWP 0 (e.g., at a time o+q). BWPs are described asexample resources, and any wireless resource may be applicable to one ormore procedures described herein.

FIG. 20 shows an example of BWP switching. The BWP switching may beperformed on an SCell. A base station 2002 may send (e.g., transmit) oneor more messages (e.g., one or more RRC messages) 2012 for configuringmultiple BWPs (e.g., multiple BWPs comprising a DL BWP 0, a DL BWP 1, aDL BWP 2, a DL BWP 3, an UL BWP 0, an UL BWP 1, an UL BWP 2, and an ULBWP 3 shown in tables 2006 and 2008, respectively). The multiple BWPsmay be BWPs of an SCell. The DL (and/or UL) BWP 0 may be a default BWP.The DL (and/or UL) BWP 1 may be a first (or initial) active BWP (e.g., afirst DL BWP or a first UL BWP). A wireless device 2004 may determinethe multiple BWPs configured for the wireless device 2004, for example,based on the one or more messages 2012. The base station 2002 may send,to the wireless device 2004, a MAC CE 2014 for activating the SCell(e.g., at a time n). The wireless device 2004 may activate the SCell(e.g., at a time n+k). The wireless device 2004 may start to monitor aPDCCH on (e.g., sent via) the DL BWP 1. The base station 2002 may sendDCI 2016 for a DL assignment (e.g., at a time m). The DCI 2016 may besent via the DL BWP 1 (e.g., a first DL BWP). The wireless device 2004may receive a packet via the DL BWP 1 or via another active DL BWP(e.g., at a time m+l), for example, based on the DL assignment. Thewireless device 2004 may start a BWP inactivity timer (e.g., at the timem+l). The wireless device 2004 may start the BWP inactivity timer, forexample, after receiving scheduled downlink packets. The base station2002 may send DCI 2016 for an UL grant (e.g., at the time m). The DCI2016 may be sent via the DL BWP 1 (e.g., a first DL BWP or an initial DLBWP). The wireless device 2004 may send a packet via an UL BWP 1 (e.g.,via a first UL BWP or an initial UL BWP at a time m+l), for example,based on the UL grant. The wireless device 2004 may start a BWPinactivity timer (e.g., at the time m+l). The wireless device 2004 maystart the BWP inactivity timer, for example, after sending scheduleduplink packets.

The BWP inactivity timer may expire (e.g., at a time s). The BWPinactivity may expire, for example, if the wireless device 2004 does notperform reception or transmission for a period of time (e.g., a periodfrom the time m+l to the time s). The wireless device 2004 may switchthe DL BWP 1 to the DL BWP 0 (e.g., a default BWP). The fallback to theDL BWP 0 may occur (e.g., at a time s+t), for example, after the BWPinactivity timer expires. The base station 2002 may send, to thewireless device 2004, a MAC CE 2018 for deactivating the SCell (e.g., ata time o). The wireless device 2004 may deactivate the SCell and/or stopthe BWP inactivity timer (e.g., at a time o+p). The wireless device 2004may deactivate the SCell and/or stop the BWP inactivity timer, forexample, after receiving and/or checking an indication of the MAC CE2018.

FIG. 21A and FIG. 21B show examples of a system for random accessprocedure with BWP switching. The wireless device 2126 may switch to adownlink BWP based on a linkage between the downlink BWP and an activeuplink BWP, for example, based on starting a random access procedure.The wireless device 2126 and the base station 2124 may be configured touse a first uplink BWP 2102, a second uplink BWP 2106, a third uplinkBWP 2110, a first downlink BWP 2104, a second downlink BWP 2108, and/ora third downlink BWP 2112. The wireless device 2126 may receive an RRCmessage from the base station 2114, for example, at time T₀ (2114),configuring the BWPs. The base station 2124 may cause the first downlinkBWP 2104 and the second uplink BWP 2106 to become active between thebase station 2124 and the wireless device 2126, for example, at time T₁(2116). The wireless device 2126 may initiate a random access procedure,for example, at time T₂ (2118), and begin switching from the firstdownlink BWP 2104 to the second downlink BWP 2108, for example, based ona linkage between the second uplink BWP 2106 and the second downlink BWP2108 (e.g., numerology, shared control channel, etc.). The wirelessdevice 2126 may send a preamble transmission to the base station 2124via the second uplink BWP 2106, for example, at time T₃ (2120). The basestation 2124 may send a random access response (RAR) via the seconddownlink BWP 2108, for example, at time T₄.

A wireless device may operate (e.g., communicate, transmit and/orreceive, send messages, etc.) via a first uplink BWP of a cell and afirst downlink BWP of the cell. The wireless device may initiate and/orperform a random access procedure (e.g., contention based,contention-free, etc.) via the first uplink BWP. The wireless device mayswitch from the first downlink BWP to an initial downlink BWP and/orswitch from the first uplink BWP to an initial uplink BWP, for example,based on one or more PRACH occasions not being configured, by a basestation, for the first uplink BWP. The wireless device may perform therandom access procedure via the initial uplink BWP and the initialdownlink BWP.

A wireless device may operate via a first uplink BWP of a cell and afirst downlink BWP of the cell. The first uplink BWP may be indicated(e.g., identified) by a first uplink BWP-specific index. The firstdownlink BWP may be indicated (e.g., identified) by a first downlinkBWP-specific index. The wireless device may initiate a random accessprocedure (e.g., contention based, contention-free, etc.) via the firstuplink BWP. The wireless device may perform the random access procedurevia the first uplink BWP and the first downlink BWP, for example, basedon one or more PRACH occasions being configured, by a base station, forthe first uplink BWP, and/or based on the first uplink BWP-specificindex being the same as the first downlink BWP-specific index.

A wireless device may operate via a first uplink BWP of a cell and afirst downlink BWP of the cell. The first uplink BWP may be indicated(e.g., identified) by a first uplink BWP-specific index. The firstdownlink BWP may be indicated (e.g., identified) by a first downlinkBWP-specific index. The wireless device may initiate a random accessprocedure (e.g., contention based, contention-free, etc.) via the firstuplink BWP. The wireless device may switch from the first downlink BWPto a third downlink BWP of the cell associated with a third downlinkBWP-specific index, for example, based on one or more PRACH occasionsbeing configured, by a base station, for the first uplink BWP, and/orbased on the first downlink BWP-specific index being different from thefirst uplink BWP-specific index. The third downlink BWP-specific indexmay be same as or different from the first uplink BWP-specific index.The wireless device may perform the random access procedure via thefirst uplink BWP and the third downlink BWP, for example, based on theswitching. The random access procedure may be a contention-based randomaccess procedure. The base station and the wireless device may operatein a paired spectrum (e.g., frequency division duplex (FDD)).

FIG. 22 shows an example method for BWP switching for a random accessprocedure. A wireless device may determine to switch or to refrain fromswitching to a downlink BWP, based starting a random access procedureand based on a BWP-ID match between an active downlink BWP and an activeuplink BWP. The method may be accomplished by systems and apparatusesdescribed herein, for example, the base station 2124 and wireless device2126 of FIGS. 21A and/or FIG. 21B. At step 2202, the wireless device mayreceive an RRC configuration regarding the BWPs. At step 2204, thewireless device may activate a first uplink BWP and a first downlinkBWP. At step 2206, the wireless device may initiate a random accessprocedure via the first uplink BWP. At step 2208, the wireless devicemay determine that the PRACH occasions are configured for the firstuplink BWP. At step 2210, the wireless device may determine that theBWP-ID of the first downlink BWP is not equal to the BWP-ID of the firstuplink BWP. At step 2212, the wireless device may switch to a thirddownlink BWP with a same BWP-ID as the first uplink BWP. At step 2214,the wireless device may perform the random access procedure.

Alternate processes may also be possible using the method. At step 2210,the wireless device may determine that the BWP-ID of the first downlinkBWP is equal to the BWP-ID of the first uplink BWP. At step 2214, thewireless device may perform the random access procedure. At step 2208,the wireless device may determine that the PRACH occasions are notconfigured for the first uplink BWP. At step 2216, the wireless devicemay switch to an initial downlink BWP and/or switch to an initial uplinkBWP. At step 2214, the wireless device may perform the random accessprocedure.

A problem may arise in existing systems, for example, if an uplink BWPindex (ID) and a downlink BWP ID do not match during beam failurerecovery (BFR) or random access procedures (e.g., as part of celladdition, handover, reconfigured with sync, etc.). The wireless devicemay trigger a downlink BWP switching to a linked downlink BWP with theBWP ID that is the same as a first active uplink BWP index (e.g.,firstActiveUplinkBWP-ID), for example, based on a first active downlinkBWP index (e.g., firstActiveDownlink BWP-ID) and the first active uplinkBWP index (e.g., firstActiveUplink BWP-ID) being different if (e.g., ata time that) the wireless device initiates a random access procedure fora BFR of the downlink BWP. The downlink BWP switching may delay therandom access procedure.

As described herein, a base station may send (e.g., transmit) areconfiguration message (e.g., RRC reconfiguration message) to awireless device. The base station may send the reconfiguration message,for example, before the BFR procedure and/or before the random accessprocedure. The base station may set an active uplink BWP index (e.g.,firstActiveUplinkBWP-ID) and an active downlink BWP index (e.g.,firstActiveDownlink BWP-ID) to the same value. The base station may sendthe reconfiguration message, for example, based on a determination thatthe wireless device may perform the BFR procedure and/or the randomaccess procedure (e.g., within a determined amount of time). The basestation may send the reconfiguration message, for example, based on athreshold value comparison with an attribute of the wireless device orbase station, a measurement of signal at the wireless device (e.g.,error rate, signal strength, etc.), and/or a measurement of signal(e.g., error rate, signal strength, etc.) at the base station. Forexample, a millimeter base station may have a small radius of coverage.The base station may send a reconfiguration message to a wireless devicethat sets an active uplink BWP index (e.g., firstActiveUplinkBWP-ID) andan active downlink BWP index (e.g., firstActiveDownlink BWP-ID) to thesame value, for example, based on a detected mobility of the wirelessdevice (e.g., a threshold comparison with a signal strength, signalquality, change in position). This setting of the active uplink BWPindex (e.g., firstActiveUplinkBWP-ID) and the active downlink BWP index(e.g., firstActiveDownlink BWP-ID) to the same value may reduce delaycaused by BWP switching before a random access procedure.

FIG. 23 shows an example of a BWP linkage in a paired spectrum (e.g.,FDD) for a BFR procedure. The base station may configure the wirelessdevice to use or make active an UL BWP (e.g., UL-BWP-1 2302) linked witha DL BWP (e.g., DL-BWP-1 2304). The wireless device may avoid a delayfrom BWP switching, for example, if the wireless device determines toperform a BFR procedure and/or a random access procedure.

A wireless device may receive one or more messages comprisingconfiguration parameters of a cell from a base station. Theconfiguration parameters may comprise BWP configuration parameters for aplurality of DL BWPs and a plurality of UL BWPs. The plurality of DLBWPs may comprise DL-BWP-1 2304, DL-BWP-2 2308, and/or DL-BWP-3 2312.The plurality of UL BWPs may comprise UL-BWP-1 2302, UL-BWP-2 2306,and/or UL-BWP-3 2310. UL-BWP-1 2302 and DL-BWP-1 2304 may be linked.UL-BWP-2 2306 and DL-BWP-2 2308 may be linked. UL-BWP-3 2310 andDL-BWP-3 2312 may be linked. The BWP configuration parameters mayinclude an index of an uplink BWP and an index of a downlink BWP. Theindex of the uplink BWP and the index of the downlink BWP may be linked.The index of the uplink BWP and the index of the downlink BW may not belinked. The index of the uplink BWP and the index of the downlink BW maybe different indexes. The index of the uplink BWP and the index of thedownlink BWP may be the same index.

The DL-BWP-1 2304, the DL-BWP-2 2308, and the DL-BWP-3 23012 may beindicated by a DL-BWP-1 index, DL-BWP-2 index, and DL-BWP-3 index (e.g.,provided by a higher layer parameter BWP-ID), respectively. The UL-BWP-12302, the UL-BWP-2 2308, and the UL-BWP-3 2312 may be indicated by aUL-BWP-1 index, UL-BWP-2 index, and UL-BWP-3 index (e.g., provided by ahigher layer parameter BWP-ID), respectively. The DL-BWP-1 index and theUL-BWP-1 index may be the same. The DL-BWP-2 index and the UL-BWP-2index may be the same. The DL-BWP-3 index and the UL-BWP-3 index may bethe same. The DL-BWP-1 index and the UL-BWP-1 index being the same maybe an indicator of linked uplink and downlink BWPs.

The configuration parameters may comprise DL-BWP-specific BFRconfiguration parameters (e.g., RadioLinkMonitoringConfig) for at leastone of the plurality of DL BWPs (e.g., DL-BWP-1 2304, DL-BWP-2 2308,DL-BWP-3 2312). The DL-BWP-specific BFR configuration parameters may beBWP specific. The DL-BWP-specific BFR configuration parameters may beBWP dedicated.

First DL-BWP-specific BFR configuration parameters for the DL-BWP-1 2304may comprise one or more first RSs (e.g., RadioLinkMonitoringRS) of theDL-BWP-1 2304 and a first beam failure instance (BFI) counter (e.g.,beamFailurelnstanceMaxCount). The wireless device may assess the one ormore first RSs (e.g., SSBs, CSI-RSs) to detect a beam failure of theDL-BWP-1 2304.

Second DL-BWP-specific BFR configuration parameters for the DL-BWP-22308 may comprise one or more second RSs (e.g., RadioLinkMonitoringRS)of the DL-BWP-2 2308 and a second BFI counter (e.g.,beamFailurelnstanceMaxCount). The wireless device may assess the one ormore second RSs (e.g., SSBs, CSI-RSs) to detect a beam failure of theDL-BWP-2 2308.

Third DL-BWP-specific BFR configuration parameters for the DL-BWP-3 2312may comprise one or more third RSs (e.g., RadioLinkMonitoringRS) of theDL-BWP-3 2312 and a second BFI counter (e.g.,beamFailurelnstanceMaxCount). The wireless device may assess the one ormore third RSs (e.g., SSBs, CSI-RSs) to detect a beam failure of theDL-BWP-3 2312.

The configuration parameters may comprise UL-BWP-specific BFRconfiguration parameters (e.g., BeamFailureRecoveryConfig) for at leastone of the plurality of UL BWPs (e.g., UL-BWP-1 2302, UL-BWP-2 2306,UL-BWP-3 2310). The UL-BWP-specific BFR configuration parameters may beBWP specific. The UL-BWP-specific BFR configuration parameters may beBWP dedicated.

First UL-BWP-specific BFR configuration parameters for the UL-BWP-1 2302may comprise one or more first candidate RSs (e.g., candidateBeamRSList)of the DL-BWP-1 2302 and a first search space set (e.g.,recoverySearchSpaceID) on the DL-BWP-1 2302 in response to the DL-BWP-1index and UL-BWP-1 index being same. A second UL-BWP-specific BFRconfiguration parameters for the UL-BWP-2 2306 may comprise one or moresecond candidate RSs (e.g., candidateBeamRSList) of the DL-BWP-2 2306and a second search space set on the DL-BWP-2 2306 in response to theDL-BWP-2 index and UL-BWP-2 index being same. A third UL-BWP-specificBFR configuration parameters for the UL-BWP-3 2310 may comprise one ormore third candidate RSs (e.g., candidateBeamRSList) of the DL-BWP-32310 and a second search space set on the DL-BWP-3 2310 in response tothe DL-BWP-3 index and UL-BWP-3 index being same.

The UL-BWP-1 2302 and the DL-BWP-1 2304 may be linked/paired, forexample, in a paired spectrum (e.g., FDD) and in response to theUL-BWP-1 2302 being configured with BFR parameters (e.g., the one ormore first candidate RSs, the first search space set) of the DL-BWP-12304. The DL-BWP-1 index and the UL-BWP-1 index may be the same, forexample, based on the DL-BWP-1 2304 and the UL-BWP-1 2302 being linked.

BWP switching may be common for the DL-BWP-1 and the UL-BWP-1, forexample, based on the DL-BWP-1 and the UL-BWP-1 being linked. Thewireless device may switch the DL-BWP-1 and the UL-BWP-1 simultaneously,in succession, in response to or based on the DL-BWP-1 2304 beinglinked/paired with the UL-BWP-1 2302. In FIG. 23, the DL-BWP-2 2308 andthe UL-BWP-2 2306 may be linked/paired and the DL-BWP-3 2312 and theUL-BWP-3 2310 may be linked/paired.

One or more linked BWPs may comprise a first pair of the DL-BWP-1 2304and the UL-BWP-1 2306; a second pair of the DL-BWP-2 2308 and theUL-BWP-2 2306; and a third pair of the DL-BWP-3 2312 and the UL-BWP-32310. The wireless device may operate on at least one of the one or morelinked BWPs (e.g., DL-BWP-1 2304 and UL-BWP-1 2302, DL-BWP-2 2308 andUL-BWP-2 2306, or DL-BWP-3 2312 and UL-BWP-3 2310 in FIG. 23)simultaneously. The DL-BWP-1 2304 and the UL-BWP-1 2302 may be active,for example at a first time (e.g., slot). The, DL-BWP-2 2308 and theUL-BWP-2 2306 may be active, for example, at a second time. The DL-BWP-32312 and the UL-BWP-3 2310 may be active, for example, at a third time

The wireless device may operate on the DL-BWP-1 2304 and the UL-BWP-12306 simultaneously. The DL-BWP-1 2304 and the UL-BWP-1 2302 may be anactive DL BWP and an active UL BWP, respectively in response to theoperating. The wireless device may switch the active UL BWP from theUL-BWP-1 2302 to the UL-BWP-2 2306, for example, in response to theDL-BWP-2 2308 being linked to the UL-BWP-2 2306 (e.g., based on thewireless device switching the active DL BWP from the DL-BWP-1 2304 tothe DL-BWP-2 2308). The switching may be triggered, for example, inresponse to receiving a DCI indicating a BWP switch, an expiry of BWPinactivity timer associated with the DL-BWP-1 2304, or receiving an RRCmessage.

A primary SCG cell may be an SCG cell in which the wireless deviceperforms random access. The primary SCG cell may perform areconfiguration with Sync procedure during dual connectivity operation.A purpose of this procedure may be to modify an RRC connection, forexample, to establish, modify, and/or release RBs; to performreconfiguration with sync; to setup, modify, and/or releasemeasurements; and/or to add, modify, and/or release SCells and cellgroups. The NAS dedicated information may be transferred from a networkto the wireless device.

A cell group configuration (e.g., CellGroupConfig IE) may be used toconfigure a master cell group (MCG) or secondary cell group (SCG). Acell group may comprise at least one MAC entity, a set of logicalchannels with associated RLC entities, a primary cell (SpCell) and/orone or more secondary cells (SCells).

A RACH configuration (e.g., rach-ConfigDedicated configuration) orparameter may be a random access configuration to be used for thereconfiguration with sync (e.g., handover). The wireless device mayperform the RA according to these parameters in a first active uplinkBWP (e.g., firstActiveUplinkBWP), which may be found in a configuration(e.g., UplinkConfig).

The wireless device may perform actions after reception of an RRCreconfiguration message by the wireless device. For example, if thewireless device is configured with E-UTRA nr-SecondaryCellGroupConfig(MCG is E-UTRA) and if RRCReconfiguration was received via SRB1, thewireless device may send the RRCReconfigurationComplete via the E-UTRAMCG embedded in a E-UTRA RRC message (e.g.,RRCConnectionReconfigurationComplete). If reconfigurationWithSync isincluded in spCellConfig of an SCG, the wireless device may initiate therandom access procedure on the SpCell.

A serving cell configuration (e.g., ServingCellConfig IE) may be used toconfigure (e.g., add and/or modify) the wireless device with a servingcell, which may be the SpCell or an SCell of an MCG or SCG. Serving cellconfiguration parameters may be wireless device specific and/or cellspecific (e.g., in additionally configured bandwidth parts). A servingcell configuration (e.g., ServingCellConfig IE) may include an activedownlink BWP (e.g., firstActiveDownlinkBWP-Id) parameter and an activeuplink BWP (e.g., firstActiveUplinkBWP-Id) parameter. The activedownlink BWP parameter (e.g., firstActiveDownlinkBWP-Id field) maycomprise the ID of the DL BWP to be activated upon performing the RRC(re-)configuration, for example, based on being configured for anSpCell. The RRC (re-)configuration may not impose a BWP switch, if theactive downlink BWP parameter (e.g., firstActiveDownlinkBWP-Id field) isabsent. The active downlink BWP parameter (e.g.,firstActiveDownlinkBWP-Id field) may comprise the ID of the downlinkbandwidth part to be used upon MAC-activation of an SCell, for example,based on being configured for an SCell. An initial bandwidth part may bereferred to by a zero index (e.g., BWP-Id=0). After reconfiguration(e.g., reconfigurationWithSync) (e.g., PCell handover,PSCelladdition/change), the network may set the active downlink BWPindex (e.g., firstActiveDownlinkBWP-Id) and the active uplink BWP index(e.g., firstActiveUplinkBWP-Id) to a same value. The active uplink BWPindex (e.g., firstActiveUplinkBWP-Id field) may contain the ID of the ULBWP to be activated after performing the RRC (re-) configuration, forexample, based on being configured for an SpCell. If the field isabsent, the RRC (re-) configuration may not impose a BWP switch.

A network may provide system information through dedicated signalingusing the RRCReconfiguration message, for example, for a wireless devicein RRC_CONNECTED. The network may provide system information based onthe wireless device having an active BWP with no common search spaceconfigured to monitor system information or paging.

A network may initiate the RRC reconfiguration procedure to a wirelessdevice in RRC_CONNECTED. The network may apply the procedure as follows.The network may perform the establishment of RBs (other than SRB1, thatmay be established during RRC connection establishment), for example,only if AS security has been activated. The network may perform theaddition of Secondary Cell Group and SCells if AS security has beenactivated. The reconfigurationWithSync may be included insecondaryCellGroup if at least one DRB is setup in the SCG. ThereconfigurationWithSync may be included in a masterCellGroup, forexample, only if AS security has been activated, and SRB2 with at leastone DRB is setup and/or not suspended.

The BWP switching for a serving cell may be used to activate an inactiveBWP and/or deactivate an active BWP. The BWP switching may be controlledby the PDCCH indicating a downlink assignment or an uplink grant, by thebwp-InactivityTimer, by RRC signaling, and/or by the MAC entity itselfupon initiation of Random Access procedure. After RRC (re-)configuration of firstActiveDownlinkBWP-Id and/orfirstActiveUplinkBWP-Id for SpCell or activation of an SCell, the DL BWPand/or UL BWP indicated by firstActiveDownlinkBWP-Id and/orfirstActiveUplinkBWP-Id, respectively, may be active without receivingPDCCH indicating a downlink assignment or an uplink grant. The activeBWP for a serving cell may be indicated, for example, by either RRC orPDCCH message. A DL BWP may be paired with an UL BWP, for example, forunpaired spectrum. BWP switching may be common for both UL and DL.

After initiation of the random access procedure on a serving cell and/orafter the selection of carrier for performing Random Access procedure, abase station and/or a wireless device (e.g., MAC entity of the basestation and/or the wireless device) may perform the following for theselected carrier of this Serving Cell. If the serving cell is an SCell,the base station and/or the wireless device (e.g., MAC entity of thebase station and/or the wireless device) may stop thebwp-InactivityTimer associated with the active DL BWP of SpCell. Ifrunning, the base station and/or the wireless device (e.g., MAC entityof the base station and/or the wireless device) perform the randomaccess procedure on the active DL BWP of SpCell and active UL BWP ofthis serving cell.

The wireless device may perform the following actions after reception ofthe RRCReconfiguration. If the wireless device is configured with E-UTRAnr-SecondaryCellGroupConfig (MCG is E-UTRA) and if RRCReconfigurationwas received via SRB1, the wireless device may sendRRCReconfigurationComplete via the E-UTRA MCG embedded in E-UTRA RRCmessage RRCConnectionReconfigurationComplete. If reconfigurationWithSyncis included in spCellConfig of an SCG, the wireless device may initiatethe random access procedure on the SpCell.

The wireless device may use the SpCell configuration. For example, ifthe SpCellConfig contains spCellConfigDedicated, the wireless device mayconfigure the SpCell in accordance with the spCellConfigDedicated. Thewireless device may consider the bandwidth part indicated infirstActiveUplinkBWP-Id, for example, if configured to be the activeuplink bandwidth part. The wireless device may consider the bandwidthpart indicated in firstActiveDownlinkBWP-Id, for example, if configuredto be the active downlink bandwidth part.

The base station and/or the wireless device (e.g., MAC entity of thebase station and/or the wireless device) may perform a random accesspreamble transmission. The base station and/or the wireless device(e.g., MAC entity of the base station and/or the wireless device) may,for each random access preamble, instruct the physical layer to send(e.g., transmit, etc.) the random access preamble using the selectedPRACH occasion, corresponding RA-RNTI (if available), PREAMBLE_INDEXand/or PREAMBLE_RECEIVED_TARGET_POWER.

A device (e.g., a base station and/or a wireless device) at Layer 1 mayreceive, from higher layers, a set of SS/PBCH block indexes and mayprovide to higher layers a corresponding set of RSRP measurements, forexample, prior to initiation of the physical random access procedure. Adevice (e.g., a base station and/or a wireless device) at Layer 1 mayreceive the following information from the higher layers, for example,prior to initiation of the physical random access procedure:configuration of physical random access channel (PRACH) transmissionparameters (e.g., PRACH preamble format, time resources, and/orfrequency resources for PRACH transmission); parameters for determiningthe root sequences and their cyclic shifts in the PRACH preamblesequence set (index to logical root sequence table, cyclic shift; and/orset type (unrestricted, restricted set A, or restricted set B)). Fromthe physical layer perspective, the L1 random access procedure mayinclude the transmission of random access preamble (Msg1) in a PRACH,random access response (RAR) message with a PDCCH/PDSCH (Msg2), and, ifapplicable, the transmission of a PUSCH scheduled by a RAR UL grant, andPDSCH for contention resolution.

A wireless device may attempt to detect a DCI format 1_0 with CRCscrambled by a corresponding RA-RNTI during a window controlled byhigher layers, for example, after or in response to a PRACHtransmission. The window may start at a first symbol of the earliestCORESET the wireless device is configured to receive PDCCH forType1-PDCCH CSS set, that is at least one symbol, after the last symbolof the PRACH occasion corresponding to the PRACH transmission, in whichthe symbol duration may correspond to the SCS for Type1-PDCCH CSS set.The length of the window in number of slots, based on the SCS forType1-PDCCH CSS set, may be provided by ra-ResponseWindow. The wirelessdevice may pass the transport block to higher layers, for example, ifthe wireless device detects the DCI format 1_0 with CRC scrambled by thecorresponding RA-RNTI and/or a transport block in a corresponding PDSCHwithin the window. The higher layers may parse the transport block for arandom access preamble identity (RAPID) associated with the PRACHtransmission. The higher layers may indicate an uplink grant to thephysical layer, if the higher layers identify the RAPID in RARmessage(s) of the transport block. This may be referred to as randomaccess response (RAR) UL grant in the physical layer.

After initiation of the random access procedure on a serving cell and/orafter the selection of carrier for performing random access procedure,the base station and/or the wireless device (e.g., a MAC entity of thebase station and/or the wireless device) may, for the selected carrierof this serving cell stop an inactivity timer (e.g.,bwp-InactivityTimer) associated with the active DL BWP of this servingcell, if running. If the serving cell is an SCell, the base stationand/or the wireless device (e.g., a MAC entity of the base stationand/or the wireless device) may, for the selected carrier of thisserving cell, stop the inactivity timer (e.g., bwp-InactivityTimer)associated with the active DL BWP of SpCell, if running. The basestation and/or the wireless device (e.g., a MAC entity of the basestation and/or the wireless device) may, for the selected carrier ofthis serving cell, perform the random access procedure on the active DLBWP of SpCell and active UL BWP of this serving cell.

A wireless device may initialize BFR parameters, such as timers,counters, BFR search space, etc., for example, if a wireless deviceinitiates a random access procedure for a BFR procedure. The wirelessdevice may monitor the timers, counters, BFR search space, etc., tocomplete the BFR procedure. The base station may not be aware of the BFRprocedure being performed by the wireless device. The base station maytransmit a message to the wireless device reconfiguring the BFRparameters, such as the BFR search space, for example, during theongoing BFR procedure. Additionally, or alternatively, the base stationmay transmit a reconfiguration message, for example, if the base stationdetermines that the wireless device is moving (e.g., high speed) orrotating. Additionally, or alternatively, the base station may transmitthe reconfiguration message, for example, if the new BFR search spacehas a better channel quality than the old BFR search space based onchannel measurements. The wireless device may not switch to the new BFRparameters because the wireless device has initialized the random accessprocedure using the previous BFR parameters. The wireless device maycontinue to monitor a search space for a BFR response (e.g., DCI) fromthe base station, in which the base station may not transmit (e.g.,because the base station reconfigured the search space). This lack ofsynchronization between the base station and the wireless device mayresult in unsuccessful completion of the BFR procedure. In existingsystems, an unsuccessful completion of the BFR procedure may lead to aradio link failure (RLF). The wireless device may initiate are-connection with the base station, for example, if the unsuccessfulBFR procedure leads to a RLF. Re-connecting to the base station may takea significant amount of time to complete (e.g., seconds).

The wireless device may stop an ongoing BFR procedure and initiate a newBFR procedure, with the new BFR search space, for example, if the basestation reconfigures the BFR search space (e.g., CORESET during anongoing BFR procedure). The wireless device stops the ongoing BFRprocedure, for example, if the base station reconfigures beam failuredetection beams (or reference signals) during an ongoing BFR procedure.

A wireless device may detect a beam failure. The wireless device mayinitiate a BFR procedure to identify a new beam or beam pair. As part ofthe BFR procedure, the wireless device may transmit a beam recoveryrequest to the network. The wireless device may wait for a response tothe beam recovery request. If a response is received, the beam failurerecovery may be a success. If a response is not received, the beamfailure recovery may be unsuccessful, and the wireless device maytransmit another beam-recovery request to the network. In at least someinstances, a base station may transmit one or more messages to thewireless device. The one or more messages may include one or more BFRconfiguration parameters. Additionally, or alternatively, the one ormore messages may reconfigure one or more BFR parameters. The wirelessdevice may stop (e.g., abort, terminate, cease, etc.) the BFR procedure,for example, after or in response to receiving the one or more messagesfrom the base station. The wireless device may initiate a second BFRprocedure, for example, based on the one or more messages received fromthe base station. The second BFR procedure may be successful, forexample, based on or in response to receiving a BFR response from one ormore base stations. By aborting an initial BFR procedure and initiatinga second BFR procedure, for example, based on or in response toreceiving one or more messages from a base station, the wireless devicemay recover from the beam failure more quickly, and/or consume fewerresources (e.g., power) during the BFR procedure, than by continuing theinitial BFR procedure. The wireless device may also avoid declaring aRLF by aborting the initial BFR procedure and initiating the second BFRprocedure.

An uplink BWP (e.g., UL-BWP-1) and a downlink BWP (e.g., DL-BWP-1) maybe linked, for example, based on the uplink BWP being configured withBFR parameters (e.g., the one or more first candidate RSs, the firstsearch space set associated with the DL-BWP-1) of the downlink BWP. Awireless device may initiate a contention-free random access procedurefor a beam failure recovery of the downlink BWP, for example, based onthe uplink BWP being configured with the BFR parameters (e.g., the firstsearch space set associated with the DL-BWP-1) of the downlink BWP. Thewireless device may avoid BWP switching to a second downlink BWP (e.g.,DL-BWP-2), for example, based on the uplink BWP being linked with thedownlink BWP, for example, after or in response to the wireless deviceinitiating the contention-free random access procedure.

A base station may not configure the BFR parameters for the uplink BWP.A wireless device may initiate a contention-based random accessprocedure for a beam failure recovery of the downlink BWP, for example,based on the uplink BWP not being configured with the BFR parameters ofthe downlink BWP. Alternatively, the base station may configure the BFRparameters on the uplink BWP. A search space set (e.g., the first spaceset) associated with a BFR procedure may be absent in the BFR parametersconfigured by the base station. A wireless device may initiate acontention-based random access procedure for a beam failure recovery ofthe downlink BWP, for example, based on the search space set beingabsent in the BFR parameters of the uplink BWP.

A wireless device may be active on a first downlink BWP (e.g., theDL-BWP-1) identified and/or indicated by a first downlink BWP index. Awireless device may also be active on a first uplink BWP (e.g., theUL-BWP-2) identified and/or indicated by a first uplink BWP index. Thefirst downlink BWP index and the first uplink BWP index may bedifferent. The wireless device may switch from the first downlink BWP toa second downlink BWP (e.g., the DL-BWP-2) identified and/or indicatedby a second downlink BWP index, for example, if the wireless deviceinitiates a contention-based random access procedure for a beam failurerecovery of the first downlink BWP. The second downlink BWP index may bethe same as the first uplink BWP index. BWP switching may be common inresponse to the linkage between the downlink BWP and the uplink BWP.

The wireless device may stop (e.g., abort) the contention-based randomaccess procedure for the beam failure recovery of the first downlinkBWP, for example, after or in response to switching from the firstdownlink BWP to the second downlink BWP. The base station may not beaware of the switching from the first downlink BWP to the seconddownlink BWP. The wireless device may initiate a second random accessprocedure, for example, in response to the switching.

FIG. 24 shows an example of a BWP linkage in a paired spectrum (e.g.,FDD) for a BFR procedure. A base station may have to separate thedownlink transmissions in time, for example, if a large quantity ofclosely-spaced antenna elements may be providing downlink transmissionsto different devices located in different directions. A base station mayestablish a suitable beam pair (e.g. transmitter/receiver beam pair) foreach device, for example, as part of beam management. The suitable beampair may be a suitable downlink bandwidth part (DL-BWP) and a suitableuplink bandwidth part (UP-BWP). FIG. 24 shows that uplink bandwidth part(UL-BWP-1) 2402 and downlink bandwidth part (DL-BWP-1) 2404 may belinked (e.g., paired), UL-BWP-2 2406 and DL-BWP-2 2408 may be linked(e.g., paired), and UL-BWP3 2410 and the DL-BWP-3 2412 may be linked(e.g., paired). Accordingly, a base station may provide one or morelinked BWPs (e.g., first pair UL-BWP-1 2402 and DL-BWP-1 2404; secondpair UL-BWP-2 2406 and DL-BWP-2 2408; and third pair UL-BWP-32410 andDL-BWP-3). BWP switching may be common between the first downlink BWPand the first uplink BWP, for example, if a first downlink BWP (e.g.,DL-BWP-1 2404) and a first uplink BWP (e.g., UL-BWP-12402) are linked.The wireless device may operate on the first downlink BWP (e.g.,DL-BWP-1 2404) and the first uplink BWP (e.g., UL-BWP-1 2402)simultaneously, for example, based on the first downlink BWP beinglinked (e.g., paired) with the first uplink BWP.

An uplink BWP (e.g., UL-BWP-1) and a downlink BWP (e.g., DL-BWP-1) maybe linked based on the downlink BWP being configured withDL-BWP-specific BFR configuration parameters (e.g.,RadioLinkMonitoringConfig). The DL-BWP-specific BFR configurationparameters may comprise at least one of: one or more RSs (e.g.,RadioLinkMonitoringRS) of the downlink BWP, a beam failure instance(BFI) counter (e.g., beamFailurelnstanceMaxCount), and/or a beam failuredetection timer (e.g., beamFailureDetectionTimer). The configurationparameters may comprise DL-BWP-specific BFR configuration parameters(e.g., RadioLinkMonitoringConfig) for at least one of the plurality ofDL BWPs (e.g., DL-BWP-1 2404, DL-BWP-2 2408, DL-BWP-3 2412). FirstDL-BWP-specific BFR configuration parameters for DL-BWP-1 2404 maycomprise one or more first RSs (e.g., RadioLinkMonitoringRS) and a firstbeam failure instance (BFI) counter (e.g., beamFailurelnstanceMaxCount).Second DL-BWP-specific BFR configuration parameters for DL-BWP-2 2408may comprise one or more second RSs (e.g., RadioLinkMonitoringRS) and asecond BFI counter (e.g., beamFailurelnstanceMaxCount). In someinstances, the configuration parameters may further compriseUL-BWP-specific BFR configuration parameters (e.g.,BeamFailureRecoveryConfig) for at least one of the plurality of UL BWPs(e.g., UL-BWP-1 2402, UL-BWP-2 2406, UL-BWP-3 2410). FirstUL-BWP-specific BFR configuration parameters for UL-BWP-1 2402 maycomprise one or more first candidate RSs (e.g., candidateBeamRSList) anda first search space set (e.g., recoverySearchSpaceID).

The uplink BWP and the downlink BWP may be active simultaneously. Thedownlink BWP may be an active downlink BWP if the uplink BWP is anactive uplink BWP, for example, based on the linkage. Similarly, theuplink BWP may be an active uplink BWP if the downlink BWP is an activedownlink BWP, for example, based on the linkage. The wireless device maynot switch the downlink BWP if the wireless device initiates acontention-based random access procedure for a beam failure recovery ofthe downlink BWP via the uplink BWP, for example, based on the uplinkBWP being linked with the downlink BWP. A first uplink BWP identifiedand/or indicated with a first uplink BWP index may be an active uplinkBWP, for example, if a first downlink BWP identified and/or indicatedwith a first downlink BWP index is configured with DL-BWP-specific BFRconfiguration parameters and the first downlink BWP is an activedownlink BWP. The first downlink BWP index and the first uplink BWPindex may be the same, for example, based on the first downlink BWPbeing configured with the DL-BWP-specific BFR configuration parameters.

The wireless device may operate on at least one of the one or morelinked BWPs (e.g., DL-BWP-1 2404 and UL-BWP-1 2402, DL-BWP-2 2408 andUL-BWP-2 2406, or DL-BWP-3 2412 and UL-BWP-3 2410) simultaneously.DL-BWP-1 2404 and the UL-BWP-1 2402 may be active at a first time (e.g.,slot), DL-BWP-2 2408 and UL-BWP-2 2406 may be active at a second time,and DL-BWP-3 2412 and UL-BWP-3 2410 may be active at a third time. Thewireless device may operate on DL-BWP-1 2404 and UL-BWP-1 2402simultaneously. DL-BWP-1 2404 and UL-BWP-1 2402 may be an activedownlink BWP and an active uplink BWP, respectively. If the wirelessdevice switches the active downlink BWP from DL-BWP-1 2404 to theDL-BWP-2 2408, the wireless device may also switch the active uplink BWPfrom UL-BWP-1 2402 to the UL-BWP-2 2406, for example, based on DL-BWP-22408 being linked to UL-BWP-2 2406. The switching may be triggered, forexample, after or in response to receiving a DCI indicating a BWPswitch, an expiry of BWP inactivity timer associated with DL-BWP-1 2404,and/or receiving an RRC message.

FIG. 25 shows an example of a BFR procedure. In some instances, one orboth beams in a beam pair may be disrupted. This may be due to rapidchanges in the environment or movement of the wireless device. If one orboth beams in the beam pair are disrupted, the wireless device may takesteps to recover from the beam failure. At T₀ 2502, the wireless device2510 may receive one or more messages comprising configurationparameters from a base station 2520. The one or more messages maycomprise one or more RRC messages (e.g. RRC connection reconfigurationmessage, RRC connection reestablishment message, or RRC connection setupmessage). The configuration parameters may further comprise one or moreBFR configuration parameters for a cell (e.g., PCell, PSCell, SCell).The one or more BFR configuration parameters may comprise a set of RSresource configurations for a configured downlink BWP of the cell. Theset of RS resource configurations may comprise one or more first RSs(e.g., periodic CSI-RS or SS blocks) of the configured downlink BWP. Thewireless device 2510 may measure radio link quality of the one or morefirst RSs (e.g., provided by RadioLinkMonitoringRS infailureDetectionResources) for a beam failure detection of theconfigured downlink BWP of the cell.

The wireless device 2510 may be provided (e.g., by a higher layersignaling) with one or more CORESETS for a configured downlink BWP of acell. The wireless device 2510 may be provided with a CORESET index(e.g., by higher layer parameter ControlResourceSetID) and/or a TCIstate (e.g., by higher layer parameter TCI-states) for at least one ofthe one or more CORESETS. The TCI state may be used for at least onePDCCH reception in the at least one of the one or more CORESETS. The TCIstate may indicate quasi co-location information of DM-RS antenna portfor the at least one PDCCH reception in the at least one of the one ormore CORESETS. The TCI state may indicate that the DM-RS antenna portfor the at least one PDCCH reception in the at least one of the one ormore CORESETs is quasi co-located (e.g., QCL-TypeD) with one or moredownlink RSs configured by the TCI state.

The one or more BFR configuration parameters may not comprise a set ofRS resource configurations (e.g., RadioLinkMonitoringRS infailureDetectionResources) for a configured downlink BWP of the cell.The wireless device 2510 may determine one or more first RSs to includeone or more downlink RSs, for example, based on the one or more BFRconfiguration parameters not comprising the set of RS resourceconfigurations. The one or more RSs may be configured by the TCI stateassociated with the at least one of the one or more CORESETS.

The one or more BFR configuration parameters may further comprise asecond set of RS resource configurations of a configured uplink BWP ofthe cell. The second set of RS resource configurations may comprise oneor more second RSs (e.g., periodic CSI-RS or SS blocks). The one or moresecond RSs (e.g., candidateBeamRSList) may be associated with theconfigured downlink BWP. The wireless device 2510 may measure radio linkquality of the one or more second RSs for a beam failure recovery (e.g.,of the configured downlink BWP of the cell). The one or more BFRconfiguration parameters may further comprise one or more beam failurerecovery request (BFRQ) resources (e.g., PRACH-ResourceDedicatedBFR ofthe candidateBeamRSList) on the configured uplink BWP. The one or moreBFR configuration parameters may further comprise an association betweeneach of the one or more second RSs and each of the one or more BFRQresources (e.g., the association may be one-to-one).

The wireless device 2510 (e.g., a physical layer of the wireless device2510) may assess a radio link quality of the one or more first RSsagainst a first threshold (e.g., rlmInSyncOutOfSyncThreshold). The firstthreshold (e.g. hypothetical BLER, L1-RSRP) may be a first valueprovided by a higher layer signaling (e.g. RRC, MAC). The wirelessdevice 2510 (e.g., the physical layer of wireless device 2510) mayprovide a beam failure instance (e.g., BFI) indication to a higher layer(e.g. MAC) of the wireless device 2510, for example, if the radio linkquality (e.g., BLER, L1-RSRP) of the one or more first RSs is less thanor equal to the first threshold (e.g., higher BLER, lower SINR, lowerL1-RSRP). The wireless device 2510 may provide the beam failure instanceindication to the higher layer with a periodicity. The periodicity maybe determined by the longer of the shortest periodicity among one ormore periodicities associated (e.g., one-to-one) with the one or morefirst RSs and a second value (e.g., 2 msec or any other duration). Thesecond value may be configured by the one or more RRC messages and/ormay be fixed (e.g., predefined). The wireless device 2510 (e.g., thephysical layer of the wireless device 2510) may not send a non-beamfailure instance indication to the higher layers of wireless device 250,for example, if the radio link quality (e.g., BLER, L1-RSRP) for the oneor more first RSs (e.g., periodic CSI-RS, SSB) is greater than the firstthreshold (e.g., lower BLER, higher SINR, higher L1-RSRP).

The one or more BFR configuration parameters may further comprise afirst beam failure detection timer (e.g., provided bybeamFailureDetectionTimer in RadioLinkMonitoringConfig) and a firstvalue (e.g., provided by beamFailurelnstanceMaxCount inRadioLinkMonitoringConfig) for the configured downlink BWP of the cell.Wireless device 2510 may start, or restart, the first beam failuredetection timer (e.g., beamFailureDetectionTimer) associated with theconfigured downlink BWP, for example, if the higher layer (e.g., MAC) ofwireless device 2510 receives a beam failure instance (BFI) indicationfrom the physical layer of wireless device 2510. In addition tostarting, or restarting, the first beam failure detection timer,wireless device 2510 may increment a first beam failure counter (e.g.,BFI_COUNTER) of the configured downlink BWP (e.g., by one or any othervalue). Wireless device 2510 may set the first beam failure counter tozero or any other value, for example, if the first beam failuredetection timer expires.

At time T₁ 2504, the wireless device 2510 may detect a beam failure ofthe configured downlink BWP, for example, based on the first beamfailure counter being greater than or equal to the first value (e.g.,beamFailurelnstanceMaxCount). The wireless device 2510 may initiate arandom access procedure (e.g., contention-free random access,contention-based random access) for a beam failure recovery of theconfigured downlink BWP, for example, based on the first beam failurecounter being greater than or equal to the first value.

The one or more BFR configuration parameters may comprise a beam failurerecovery timer (e.g., beamFailureRecoveryTimer provided byBeamFailureRecoveryConfig) in the configured uplink BWP. The wirelessdevice 2510 may start the beam failure recovery timer (if configured),for example, after or in response to initiating the random accessprocedure for the beam failure recovery. The one or more BFRconfiguration parameters may comprise a higher layer parameter (e.g.,recoverySearchSpaceId in BeamFailureRecoveryConfig) on the configureduplink BWP. The wireless device 2510 may be provided with a search spaceset by the higher layer parameter. The search space set may beassociated with a BFR CORESET on the configured downlink BWP. Thewireless device 2510 may be provided with the BFR CORESET through a linkto the search space set. The random access procedure may comprise acandidate beam identification procedure. The wireless device 2510 mayidentify a first RS in the one or more second RSs configured in theconfigured uplink BWP for the candidate beam identification procedure.The first RS may be associated with a BFRQ resource of the one or moreBFRQ resources. The BFRQ resource may comprise at least one preamble andat least one PRACH (e.g. time and/or frequency) resource on theconfigured uplink BWP. A second radio link quality (e.g. BLER, L1-RSRP)of the first RS may be greater (e.g. lower BLER or higher L1-RSRP orhigher SINR) than a second threshold (e.g., rsrp-ThresholdSSB). Thesecond threshold may be a second value provided by a higher layer (e.g.RRC, MAC).

The wireless device 2510 may transmit, in a first slot at time T₁ 2504,the at least one preamble via at least one PRACH resource of theconfigured uplink BWP for the random access procedure of the configureddownlink BWP, for example, after or in response to identifying the firstRSrandom access. The wireless device 2510 may start monitoring, from asecond slot (e.g., 4 slots after the first slot), for a BFR response ofthe base station, for example, after or in response to transmitting theat least one preamble in the first slot. The wireless device 2510 maymonitor the at least one of the one or more CORESETS during the randomaccess procedure for the beam failure recovery of the configureddownlink BWP (e.g., between time T₁ 2504 and T₂ 2506). The wirelessdevice 2510 may monitor the at least one of the one or more CORESETS andthe BFR CORESET (e.g., within the configured response window) during therandom access procedure for the beam failure recovery of the configureddownlink BWP (e.g., between time T₁ 2504 and T₂ 2506). Monitoring forthe BFR response may comprise monitoring at least one second PDCCHreception in the BFR CORESET (linked to the search space set) within aconfigured response window (e.g., ra-responseWindow) for a DCI (e.g. adownlink assignment or an uplink grant). The DCI may be with CRCscrambled by a C-RNTI or MCS-C-RNTI of the wireless device 2510. Theconfigured response window may be configured by the one or more BFRconfiguration parameters. The configured response window may provide ahigher layer parameter (e.g., BeamFailureRecoveryConfig) for theconfigured uplink BWP. The first RS identified (e.g. indicated) in thecandidate beam identification procedure may be associated (e.g. quasico-located) with at least one DM-RS of the at least one second PDCCHreception in the BFR CORESET monitored by the wireless device 2510.

The random access procedure for the beam failure recovery of theconfigured downlink BWP may be successfully completed, for example,after or in response to receiving the DCI, at time T₂ 2506, on the atleast one second PDCCH reception in the BFR CORESET within theconfigured response window. The wireless device 2510 may continuemonitoring at least one third PDCCH reception in the BFR CORESET (or inthe search space set) until wireless device 2510 receives a MAC CEactivation command (e.g., wireless device-specific PDCCH MAC CE) for asecond TCI state at time T₃ 2508, for example, after or in response tocompleting the random access procedure successfully. The first RSidentified (e.g. indicated) in the candidate beam identificationprocedure may be associated (e.g. quasi co-located) with at least oneDM-RS of the at least one third PDCCH reception in the BFR CORESETmonitored by the wireless device 2510. The wireless device 2510 may stopmonitoring the at least one of the one or more CORESETs, for example,after or in response to receiving the DCI on the at least one secondPDCCH reception in the BFR CORESET (e.g., at time T₂ 2506). The wirelessdevice 2510 may stop monitoring the at least one of the one or moreCORESETS, for example, after or in response to completing the randomaccess procedure successfully (e.g., at time T₂ 2506).

The wireless device 2510 may continue monitoring at least one thirdPDCCH reception in the BFR CORESET (or in the search space set), forexample, at least until the wireless device 2510 receives a higher layerparameter (e.g., TCI-StatesPDCCH-ToAddlist and/orTCI-StatesPDCCH-ToReleaseList). The wireless device 2510 may receive ahigher layer parameter (e.g., TCI-StatesPDCCH-ToAddlist and/orTCI-StatesPDCCH-ToReleaseList), for example, after or in response tocompleting the random access procedure successfully at time T₃ 2508. Thefirst RS identified and/or indicated in the candidate beamidentification procedure may be associated (e.g. quasi co-located) withat least one DM-RS of the at least one third PDCCH reception in the BFRCORESET monitored by the wireless device 2510. random access randomaccess

FIG. 26 shows an example of a downlink BFR procedure. One or both beamsin a beam pair may be disrupted, for example, in response to rapidchanges in the environment or movement of the wireless device. Thewireless device may take steps to recover from the beam failure, forexample, after or in response to detecting the beam failure. A wirelessdevice may be provided with a first CORESET index (e.g., by higher layerparameter ControlResourceSetID) for BFR CORESET 2616. The wirelessdevice may be provided, by the configuration parameters, with a secondCORESET index (e.g., by higher layer parameter ControlResourceSetID) anda TCI state (e.g., by higher layer parameter TCI-States) for the atleast one of first CORESET-1 2612 and second CORESET-2 2614 of theconfigured downlink BWP. The TCI state may be used for at least onePDCCH reception in the at least one of the one or more CORESETS. The TCIstate may indicate quasi co-location information of a DM-RS antenna portfor the at least one PDCCH reception in the at least one of the one ormore CORESETS. The TCI state may indicate that the DM-RS antenna portfor the at least one PDCCH reception in the at least one of the one ormore CORESETS may be quasi co-located (e.g., QCL-TypeD) with one or moredownlink RSs, such as Serving RS 1 2622 for first CORESET-1 2612 andServing RS 2 2624 for second CORESET-2 2614. A first PDCCH reception infirst CORESET-1 2612 may be quasi co-located (e.g., QCL-TypeD) with afirst serving RS (e.g., Serving RS 1 2622), and a second PDCCH receptionin second CORESET-2 2614 may be quasi co-located (e.g., QCL-TypeD) witha second serving RS (e.g., Serving RS 2 2624). At least one of the oneor more CORESETS may be associated with a second search space set (e.g.,provided by controlResourceSetId field in the information elementSearchSpace).

A first candidate RS (e.g., Candidate RS1 2626 and Candidate RS2 2628)may be different than the one or more downlink RSs (e.g., Serving RS 12622 and Serving RS 2 2624). The first candidate RS (e.g., Candidate RS12626 or Candidate RS2 2628) may not be associated (e.g., QCL-ed Type-D)with the one or more downlink RSs (e.g., Serving RS 1 2622 and ServingRS 2 2624). The wireless device may not monitor the search space setassociated with BFR CORESET 2616 and the second search space set (e.g.,associated with the at least one first CORESET-1 2612 and secondCORESET-2 2614) simultaneously within the configured response window(e.g., time between T₁ 2504 and T₂ 2506 in FIG. 25), for example, basedon the first candidate RS (e.g., Candidate RS 2626 and Candidate RS22628) not being associated (e.g., QCL-ed Type-D) with the one or moredownlink RSs (e.g., Serving RS 1 2622 and Serving RS 2 2624).

The wireless device may use a first receiving beam for a first receptionin the first search space set. The wireless device may use a secondreceiving beam for a second reception in the second search space set.The first receiving beam may be different from the second receivingbeam. The wireless device may not use different receiving beamssimultaneously. The wireless device may not monitor the search space setassociated with the BFR CORESET 2616 and the second search space set(e.g., associated with the at least first CORESET-1 2612 and secondCORESET-2 2614) simultaneously within the configured response window2610, for example, based on the first receiving beam being differentfrom the second receiving beam. Configured response window 2610 may beassociated with a time between T₁ 2504 and T₂ 2506 of FIG. 25. Thesecond CORESET index of the at least one of the one or more CORESETS maybe lower than the first CORESET index of BFR CORESET 2616. A firstmonitoring occasion of the search space set and a second monitoringoccasion of the second search space set may overlap in time (e.g., atleast one OFDM symbol) within the configured response window 2610. Afirst monitoring occasion of the search space set and a secondmonitoring occasion of the second search space set may be separated byless than an offset (e.g., Threshold-Sched-Offset) within the configuredresponse window 2610. The offset may be configured by higher layers(e.g., RRC).

The wireless device may determine (e.g., assume) that the DM-RS antennaport for the at least one PDCCH reception in the second search space setassociated with the at least one first CORESET-1 2612 and secondCORESET-2 2614 may be quasi co-located (e.g., QCL-TypeD) with at leastone candidate RS (e.g., the first Candidate RS 1 2626 and/or secondCandidate RS 2 2628) identified and/or indicated in the candidate beamidentification procedure for the beam failure recovery, for example,based on the first monitoring occasion of the first search space set andthe second monitoring occasion of the second search space setoverlapping in time, such as during the configured response window 2610.The first search space may be associated with the BFR CORESET 2616. Thesecond search space may be associated with CORESET-1 2612 and/orCORESET-2 2614. The wireless device may determine (e.g., assume) thatthe DM-RS antenna port for the at least one PDCCH reception in thesecond search space set associated with the at least one first CORESET-12612 and second CORESET-2 2614) may be quasi co-located (e.g.,QCL-TypeD) with at least one candidate RS (e.g., the first Candidate RS1 2626 and/or second Candidate RS 2 2628) identified and/or indicated inthe candidate beam identification procedure for the beam failurerecovery, for example, for example, if a random access procedure for abeam failure recovery is ongoing. The wireless device may determine(e.g., assume) that the DM-RS antenna port for the at least one PDCCHreception in the second search space set associated with the at leastone first CORESET-1 2612 and second CORESET-2 2614) may be quasico-located (e.g., QCL-TypeD) with the first Candidate RS 1 2626 and/orsecond Candidate RS 2 2628 identified and/or indicated in the candidatebeam identification procedure for the beam failure recovery, forexample, based on the first monitoring occasion of the search space setand the second monitoring occasion of the second search space set beingseparated by less than the offset.

The wireless device may determine (e.g., change assumption) that theDM-RS antenna port for the at least one PDCCH reception in the secondsearch space set is quasi co-located (e.g., QCL-TypeD) with the one ormore downlink RSs, for example, based on the first monitoring occasionof the search space set and the second monitoring occasion of the secondsearch space set overlapping in time, such as during the configuredresponse window 2610. The DM-RS antenna port may be associated with theat least one of the one or more CORESETS. The wireless device maydetermine (e.g., change assumption) that the DM-RS antenna port for theat least one PDCCH reception in the second search space set is quasico-located (e.g., QCL-TypeD) with the one or more downlink RSs, forexample, if a random access procedure for a beam failure recovery isongoing. The first RS may be identified and/or indicated in thecandidate beam identification procedure for the beam failure recovery.Additionally, or alternatively, the wireless device may changeassumption of the DM-RS antenna port for the at least one PDCCHreception in the second search space set associated with the at leastone of the one or more CORESETS being quasi co-located (e.g., QCL-TypeD)with the one or more downlink RSs from the one or more downlink RSs tothe first RS, for example, based on the first monitoring occasion of thesearch space set and the second monitoring occasion of the second searchspace set being separated by less than the offset.

The wireless device may stop (e.g., drop, discontinue, abort, terminate,cease, etc.) monitoring the at least one PDCCH reception in the secondsearch space set associated with the at least one of the one or moreCORESETS, for example, based on the first monitoring occasion of thesearch space set and the second monitoring occasion of the second searchspace set overlapping in time, such as during the configured responsewindow 2610. The wireless device may drop monitoring the at least onePDCCH reception in the second search space set associated with the atleast one of the one or more CORESETS, for example, if a random accessprocedure for a beam failure recovery is ongoing, Additionally, oralternatively, the wireless device may drop monitoring the at least onePDCCH reception in the second search space set associated with the atleast one of the one or more CORESETS, for example, based on the firstmonitoring occasion of the search space set and the second monitoringoccasion of the second search space set being separated less than theoffset.

The wireless device may monitor a PDCCH, for a DCI, in BFR CORESET 2616,or in the search space set associated with BFR CORESET 2616, forexample, after or in response to dropping the monitoring for the atleast one PDCCH in the second search space set. The first RS identified(e.g. indicated) in the candidate beam identification procedure may beassociated (e.g. quasi co-located) with at least one DM-RS of the PDCCHin BFR CORESET 2616 monitored by the wireless device. The wirelessdevice may be provided with a first CORESET index (e.g., by higher layerparameter ControlResourceSetID) for BFR CORESET 2616. The configurationparameters may comprise a second CORESET index (e.g., by higher layerparameter ControlResourceSetID) for the at least one of the one or moreCORESETS of the configured downlink BWP.

The base station 2510 may configure the downlink BWP with one or morebeam failure detection (BFD) parameters. The one or more BFD parameters(e.g., RadioLinkMonitoringConfig) may comprise at least one of: the oneor more first RSs (e.g., failureDetectionResources) for a beam failuredetection, the first beam failure detection timer (e.g.,beamFailureDetectionTimer), and the first value (e.g.,beamFailurelnstanceMaxCount). The first CORESET index of BFR CORESET maybe lower than the second CORESET index of the at least one firstCORESET-1 2612 and second CORESET-2 2614, for example, based on i) thefirst monitoring occasion of the search space set, associated with BFRCORESET 2616, and the second monitoring occasion of the second searchspace set, associated with at the least one first CORESET-1 2612 andsecond CORESET-2 2614, overlapping in time and ii) the configureddownlink BWP being configured with the one or more BFD parameters.Additionally, or alternatively, the first CORESET index of BFR CORESETmay be lower than the second CORESET index of the at least one firstCORESET-1 2612 and second CORESET-2 2614, for example, based on: i) thefirst monitoring occasion of the search space set and the secondmonitoring occasion of the second search space set being separated lessthan the offset, and/or ii) the configured downlink BWP being configuredwith the one or more BFD parameters. The wireless device may save powerby monitoring BFR CORESET 2616 if overlapping occurs, for example, basedon the first CORESET index of BFR CORESET 2616 being configured lowerthan the second CORESET index of the at least first CORESET-1 2612 andsecond CORESET-2 2614.

The first CORESET index of BFR CORESET 2616 may be lower than the secondCORESET index of the at least first CORESET-1 2612 and second CORESET-22614, for example, based on the configured downlink BWP being configuredwith the one or more BFD parameters. Additionally, or alternatively, thefirst CORESET index of BFR CORESET 2616 may be the lowest CORESET indexamong the second CORESET index of the at least first CORESET-1 2612 andsecond CORESET-2 2614, for example, based on the configured downlink BWPbeing configured with the one or more BFD parameters. The first CORESETindex of BFR CORESET 2616 may be lowest among one or more CORESETspecific indices of the one or more CORESETS, for example, based on theconfigured downlink BWP being configured with the one or more BFDparameters by RRC configuration. Each of the one or more CORESETS may beidentified and/or indicated by one of the one or more CORESET specificindices. The one or more CORESETS configured on the configured downlinkBWP may not comprise CORESET-0. CORESET-0 may be identified and/orindicated with a first CORESET specific index. The first CORESETspecific index may be equal to zero. The CORESET-0 may be a commonCORESET configured in PBCH (MIB) and in ServingCellConfigCommon.

The first CORESET index of BFR CORESET 2616 may be lower than the secondCORESET index of the at least one first CORESET-1 2612 and secondCORESET-2 2614, for example, based on the one or more CORESETS notcomprising the CORESET-0. The first CORESET index of BFR CORESET 2616may be lower than the second CORESET index of the at least one firstCORESET-1 2612 and second CORESET-2 2614, for example, based on theconfigured downlink BWP being configured with the one or more BFDparameters. The first CORESET index of BFR CORESET 2616 may be lowerthan the second CORESET index of the at least one first CORESET-1 2612and second CORESET-2 2614, for example, if the first monitoring occasionof the search space set associated with BFR CORESET 2616 and the secondmonitoring occasion of the second search space set associated with atthe least one first CORESET-1 2612 and second CORESET-2 2614 overlap intime. Additionally, or alternatively, if the first monitoring occasionof the search space set and the second monitoring occasion of the secondsearch space set is separated by less than the offset, the first CORESETindex of BFR CORESET 2616 may be lower than the second CORESET index ofthe at least one first CORESET-1 2612 and second CORESET-2 2614, forexample, based on the one or more CORESETS not comprising the CORESET-0and the configured downlink BWP being configured with the one or moreBFD parameters.

The first CORESET index of BFR CORESET 2616 may be lower than, or thelowest amongst, the second CORESET index of the at least one firstCORESET-1 2612 and second CORESET-2 2614, for example, based on: i) theone or more CORESETS not comprising the CORESET-0, and/or ii) theconfigured downlink BWP being configured with the one or more BFDparameters. The first CORESET index of BFR CORESET 2616 may be lowestamong the one or more CORESET specific indices of the one or moreCORESETS, for example, based on the one or more CORESETS not comprisingthe CORESET-0 and/or the configured downlink BWP being configured withthe one or more BFD parameters.

If the first monitoring occasion of the search space set and the secondmonitoring occasion of the second search space set overlap in time, arandom access procedure for a beam failure recovery may be ongoing. Thewireless device may determine (e.g., assume) that the DM-RS antenna portfor the at least one PDCCH reception in the second search space setassociated with the at least one of the one or more CORESETS is quasico-located (e.g., QCL-TypeD) with the first RS identified and/orindicated in the candidate beam identification procedure for a beamfailure recovery, for example, based on the first CORESET index of BFRCORESET 2616 being lowest value. Additionally, or alternatively, thewireless device may determine (e.g., assume) that the DM-RS antenna portfor the at least one PDCCH reception in the second search space setassociated with the at least one of the one or more CORESETS is quasico-located (e.g., QCL-TypeD) with the first RS identified and/orindicated in the candidate beam identification procedure for a beamfailure recovery, for example, if i) the first monitoring occasion ofthe search space set and the second monitoring occasion of the secondsearch space set is separated less than the offset, ii) a random accessprocedure for a beam failure recovery is ongoing, and/or iii) the firstCORESET index of BFR CORESET 2616 being lowest value amongst the one ormore CORESETs. The one or more CORESETs may comprise the CORESET-0. Thefirst monitoring occasion of the search space set and a third monitoringoccasion of a third search space set associated with the CORESET-0 mayoverlap in time. The first CORESET index of BFR CORESET 2616 may not belowest among the one or more CORESET specific indices of the one or moreCORESETS, for example, after or in response to the one or more CORESETScomprising the CORESET-0. The first CORESET specific index (e.g., 0) maybe lower than the first CORESET index.

If the first monitoring occasion of the search space set and the thirdmonitoring occasion of the third search space set associated with theCORESET-0 overlap in time, the wireless device may not monitor a PDCCH,for a DCI, in BFR CORESET 2616, or in the search space set associatedwith BFR CORESET 2616, for example, based on the first CORESET specificindex associated with the CORESET-0 being lower than the first CORESETindex associated with BFR CORESET 2616. The base station 2510 may avoidthe first monitoring occasion of the search space set and a thirdmonitoring occasion of a third search space set associated with theCORESET-0 overlapping in time, for example, based on the one or moreCORESETS comprising the CORESET-0. The first CORESET index of BFRCORESET 2616 may be second lowest among the one or more CORESET specificindices of the one or more CORESETS, for example, based on the one ormore CORESETS comprising the CORESET-0 and the configured downlink BWPbeing configured with the one or more BFD parameters.

If a random access procedure for a beam failure recovery is ongoing(e.g., between time T₁ 2504 and T₂ 2506 in FIG. 25), the wireless devicemay determine (e.g., assume) that the DM-RS antenna port for at leastone PDCCH reception in the third search space set associated with theCORESET-0 is quasi co-located (e.g., QCL-TypeD) with the first RSidentified and/or indicated in the candidate beam identificationprocedure for a beam failure recovery, for example, based on the firstmonitoring occasion of the search space set and the third monitoringoccasion of the third search space set (e.g., associated with theCORESET-0) overlapping in time. Additionally, or alternatively, thewireless device may determine (e.g., assume) that the DM-RS antenna portfor at least one PDCCH reception in the third search space setassociated with the CORESET-0 may be quasi co-located (e.g., QCL-TypeD)with the first RS identified (e.g. indicated) in the candidate beamidentification procedure for a beam failure recovery, for example, basedon the first monitoring occasion of the search space set and the thirdmonitoring occasion of the third search space set being separated byless than the offset.

If a random access procedure for a beam failure recovery is ongoing(e.g., between time T₁ 2504 and T₂ 2506 in FIG. 25) and the firstmonitoring occasion of the search space set and the third monitoringoccasion of the third search space set (e.g., associated with theCoreset-0) overlap in time, the wireless device may determine (e.g.,assume) that the DM-RS antenna port may be quasi co-located (e.g.,QCL-TypeD) with the first RS. The DM-RS antenna port may be for at leastone PDCCH reception in a third search space set associated with theCORESET-0. The first RS may be identified (e.g. indicated) in thecandidate beam identification procedure for a beam failure recovery, forexample, based on the one or more CORESETS comprising the CORESET-0. Thefirst RS may be identified and/or indicated in the candidate beamidentification procedure for a beam failure recovery, for example, basedon the first CORESET index of BFR CORESET 2616 being the second lowestamongst the one or more CORESET specific indices. If a random accessprocedure for a beam failure recovery is ongoing (e.g., between time T₁2504 and T₂ 2506 in FIG. 25) and the first monitoring occasion of thesearch space set and the third monitoring occasion of the third searchspace set is separated by less than the offset, the wireless device maydetermine (e.g., assume) that the DM-RS antenna port may be quasico-located (e.g., QCL-TypeD) with the first RS. The DM-RS antenna portmay be for at least one PDCCH reception in a third search space setassociated with the CORESET-0. The first RS may be identified and/orindicated in the candidate beam identification procedure for a beamfailure recovery, for example, based on the one or more CORESETScomprising the CORESET-0. The first RS may be identified and/orindicated in the candidate beam identification procedure for a beamfailure recovery, for example, based on the first CORESET index of BFRCORESET 2616 being the second lowest amongst the one or more CORESETspecific indices. The one or more CORESETS of the configured downlinkBWP may comprise the CORESET-0. The one or more BFR configurationparameters may not comprise a higher layer parameter (e.g.,recoverySearchSpaceId in the configured uplink BWP) indicating thesearch space set associated with BFR CORESET 2616, for example, after orin response to the one or more CORESETS comprising the CORESET-0.Parameters for search space configuration of the BFR may be absent inthe RRC messages of the BFR configuration.

The wireless device may monitor (e.g., start monitoring, beginmonitoring, resume monitoring, continue monitoring, etc.) a PDCCH for adetection of a BFR response from the base station 2510, for example,after or in response to transmitting the at least one preamble for therandom access procedure for the beam failure recovery of the configureddownlink BWP. When the one or more CORESETS of the configured downlinkBWP comprises the CORESET-0, monitoring for the BFR response maycomprise monitoring at least one second PDCCH reception in theCORESET-0, for a DCI (e.g. a downlink assignment or an uplink grant),within the configured response window 2610 (e.g., ra-responseWindow),for example, based on the one or more BFR configuration parameters notcomprising the higher layer parameter indicating the search space setassociated with BFR CORESET 2616. The DCI may be CRC scrambled by aC-RNTI or MCS-C-RNTI of the wireless device. The wireless device maydetermine that the first RS identified (e.g. indicated) in the candidatebeam identification procedure may be associated (e.g., quasi co-located)with at least one DM-RS of the at least one second PDCCH reception inthe CORESET-0 monitored by the wireless device. The random accessprocedure for the beam failure recovery of the configured downlink BWPmay be successfully completed, for example, after or in response toreceiving the DCI on the at least one second PDCCH reception in theCORESET-0 within configured response window 2610 random access.

If the higher layer parameter (e.g., recoverySearchSpaceId in theconfigured uplink BWP) indicates the search space set associated withBFR CORESET 2616 is absent in the one or more BFR configurationparameters, the wireless device may initiate a contention-free randomaccess procedure for a beam failure recovery of the configured downlinkBWP, for example, based on the one or more CORESETS of the configureddownlink BWP comprising the CORESET-0.

FIG. 27 shows an example flowchart of CORESET overlapping during adownlink beam failure recovery procedure. In step 2702, a wirelessdevice may receive one or more messages. The one or more messages may betransmitted by a base station to the wireless device. The one or moremessages may be RRC messages that comprise a plurality of configurationparameters for one or more cells. The plurality of configurationparameters may include at least one of a BFR CORESET and a first CORESETassociated with a first reference signal (RS). In step 2704, thewireless device may monitor the first CORESET based on the first RS. In2706, the wireless device may detect a beam failure. The wireless devicemay initiate a random access procedure, for example, after or inresponse to detecting the beam failure. In step 2708, the wirelessdevice may select a second RS as a candidate beam to monitor. In step2710, the wireless device may determine whether a preamble associatedwith the second RS has been transmitted. If the preamble associated withthe second RS has not been transmitted, the wireless device may notbegin monitoring the BFR CORESET. The wireless device may continue tomonitor the first CORESET, in step 2712, for example, if the preambleassociated with the second RS has not been transmitted. If the preambleassociated with the second RS signal has been transmitted, the wirelessdevice may monitor the BFR CORESET based on the second RS in step 2714.The wireless device may monitor both the first CORESET and the BFRCORESET, for example, after or in response to transmitting the preambleassociated with the second RS. In step 2716, the wireless device maydetermine whether the BFR CORESET and the first CORESET overlap in time.If there is no overlap, the wireless device may continue to monitor thefirst CORESET, based on the first RS, in step 2712. If there is overlap,the wireless device may monitor the first CORESET, based on the secondRS, in step 2718.

FIG. 28 shows an example flowchart of CORESET overlapping during adownlink beam failure recovery procedure. In step 2802, a wirelessdevice may receive one or more messages. The one or more messages may betransmitted by a base station to the wireless device. The one or moremessages may be RRC messages that comprise a plurality of configurationparameters for one or more cells. The plurality of configurationparameters may include at least one of a BFR CORESET and a first CORESETassociated with a first reference signal (RS). In step 2804, thewireless device may monitor the first CORESET based on the first RS. In2806, the wireless device may detect a beam failure. The wireless devicemay initiate a random access procedure, for example, after or inresponse to detecting the beam failure. In step 2808, the wirelessdevice may select a second RS as a candidate beam to monitor. In step2810, the wireless device may select a candidate beam and transmit apreamble associated with a second RS associated with the candidate beam.In step 2812, the wireless device may monitor the BFR CORESET, inaddition to the first CORESET, for example, after or in response totransmitting the preamble associated with the second RS. In step 2814,the wireless device may determine whether the BFR CORESET and the firstCORESET overlap in time. If there is no overlap, the wireless device maycontinue to monitor the first CORESET, based on the first RS, in step2816. If there is overlap, the wireless device may monitor the firstCORESET, based on the second RS, in step 2818.

FIG. 29 shows an example of a downlink beam failure recovery procedure.A beam failure may be caused, for example, in response to rapid changesin the environment or movement of the wireless device. A wireless devicemay initiate a beam failure recovery procedure, for example, after or inresponse to detecting the beam failure. A base station may transmit, toa wireless device, one or more messages (e.g. RRC messages) comprising aplurality of configuration parameters for at least a first cell 2910 anda second cell 2920, for example, if configured with carrier aggregation.First cell 2910 may be a SCell and second cell 2920 may be either aPCell or an SCell. First cell 2910 may be identified (e.g., indicated)by a first cell index (e.g., provided by a higher layer parameterservCellIndex), and second cell 2920 may be identified and/or indicatedby a second cell index (e.g., provided by a higher layer parameterservCellIndex). Second cell index may be lower than the first cellindex.

A wireless device may be provided, by a higher layer signaling, with oneor more second CORESETs for a downlink BWP (e.g., active DL BWP) ofsecond cell 2920. The wireless device may be provided, by the one ormore messages or configuration parameters, with a third CORESET index(e.g., by higher layer parameter ControlResourceSetID) and a TCI state(e.g., by higher layer parameter TCI-states) for at least one of the oneor more second CORESETs (e.g., CORESET-3 2972). The TCI state may beused for at least one PDCCH reception in the at least one of the one ormore second CORESETs. The TCI state may indicate quasi co-locationinformation of DM-RS antenna port for the at least one PDCCH receptionin the at least one of the one or more second CORESETs. The TCI statemay indicate that the DM-RS antenna port for the at least one PDCCHreception in the at least one of the one or more second CORESETs may bequasi co-located (e.g., QCL-TypeD) with one or more second downlink RSs(e.g., Serving RS 3 2970) configured by the TCI state. A first PDCCHreception in CORESET-3 2970 may be quasi co-located (e.g., QCL-TypeD)with Serving RS 3 2970 of second cell 2920. The at least one of the oneor more second CORESETs may be associated with a third search space set(e.g., provided by controlResourceSetId field in the information elementSearchSpace). First RS 1 2930 may be different than the one or moresecond downlink RSs (e.g., Serving RS 3 2970). First RS 1 2930 may notbe associated (e.g., QCL-ed Type-D) with the one or more second downlinkRSs (e.g., Serving RS 3 2970).

The wireless device may not monitor the search space set associated withBFR CORESET 2952 of first cell 2910 and the third search space setassociated with the at least one of the one or more second CORESETs(e.g., CORESET-3 2970) of second cell 2920 simultaneously within theconfigured response window (e.g., between time T₁ 2504 and T₂ 2506), forexample, based on the first RS not being associated (e.g., QCL-ed TypeD) with the one or more second downlink RSs. A first monitoring occasionof the search space set associated with the BFR CORESET 2952 of firstcell 2910 and a third monitoring occasion of the third search space setassociated with the at least one of the one or more second CORESETs(e.g., CORESET-3 2970) of second cell 2920 may overlap in time (e.g., atleast one OFDM symbol). The time may be within the configured responsewindow. A first monitoring occasion of the search space set and a thirdmonitoring occasion of the third search space set may be separated byless than an offset (e.g., Threshold-Sched-Offset) in time (e.g., withinthe configured response window). The offset may be configured by higherlayers (e.g., RRC).

If a random access procedure for a beam failure recovery of the cell isongoing (e.g., between time T₁ 2502 and T₂ 2504 in FIG. 25), thewireless device may determine (e.g., assume) that the DM-RS antenna portfor the at least one PDCCH reception in the third search space setassociated with the at least one of the one or more second CORESETs(CORESET-3 2972) may be quasi co-located (e.g., QCL-TypeD) with thefirst RS (e.g., Candidate RS 1 2950 or Candidate RS 2 2960) identifiedand/or indicated in the candidate beam identification procedure for thebeam failure recovery, for example, based on the first monitoringoccasion of the search space set (e.g., associated with BFR CORESET2952) of first cell 2910 and the third monitoring occasion of the thirdsearch space set (e.g., associated with CORESET-3 2972) of second cell2920 overlapping in time (e.g. within the configured response window2980) or the first monitoring occasion of the search space set and thethird monitoring occasion of the third search space set being separatedless than the offset.

If a random access procedure for a beam failure recovery of the cell isongoing (e.g., between time T₁ 2502 and T₂ 2504 in FIG. 25), thewireless device may drop monitoring the at least one PDCCH reception inthe third search space set associated with the at least one of the oneor more second CORESETs, for example, based on the first monitoringoccasion of the search space set of first cell 2910 and the thirdmonitoring occasion of the third search space set of second cell 2920overlapping in time (e.g. within the configured response window 2980) orthe first monitoring occasion of the search space set and the thirdmonitoring occasion of the third search space set being separated byless than the offset. The wireless device may monitor a PDCCH, for aDCI, in BFR CORESET 2952 (or in the search space set associated with BFRCORESET 2952) of first cell 2910, for example, after or in response todropping the monitoring of the at least one PDCCH reception in the thirdsearch space set. The first RS identified (e.g., indicated) in thecandidate beam identification procedure may be associated (e.g. quasico-located) with at least one DM-RS of the PDCCH in BFR CORESET 2952monitored by the wireless device.

FIG. 30 shows an example of a downlink beam failure recovery procedure.A wireless device may initiate a beam failure recovery procedure, forexample, after or in response to detecting a beam failure. At time T₀3002, a wireless device 3010 may receive one or more messages from thebase station 3020. The one or more messages may comprise one or moreconfiguration parameters of a cell (e.g., PCell, SCell, BWP of thecell). The one or more configuration parameters may indicate a firstCORESET identified and/or indicated with a first CORESET index and a TCIstate. The TCI state may comprise a reference signal (RS). The wirelessdevice 3010 may monitor, based on the RS, a first PDCCH in the firstCORESET for a first downlink control information (DCI). A first DM-RSantenna port for the first PDCCH in the first CORESET may be quasico-located (e.g., QCL-TypeD) with the RS indicated by the TCI state. Theone or more configuration parameters may further indicate a secondCORESET for a BFR procedure of the cell. The second CORESET may beindicated by a second CORESET index. The first CORESET index may be lessthan the second CORESET index. The one or more configuration parametersmay further indicate a beam failure instance counter (e.g.,beamFailureInstanceMaxCount) of the cell, a configured response window,and one or more BFRQ resources for the BFR procedure. The one or moreconfiguration parameters may further indicate at least: one or morefirst RSs of the cell and one or more second RSs of the cell. The one ormore first RSs may comprise one or more first CSI-RSs and/or one or morefirst SSB/PBCHs. The one or more second RSs may comprise one or moresecond CSI-RSs and/or one or more second SSB/PBCHs. The one or moreconfiguration parameters may further indicate an association betweeneach of the one or more second RSs and each of the one or more BFRQresources.

At time T₀ 3002, the wireless device 3010 may receive, from the basestation 3020, one or more first messages. The one or more first messagesmay comprise one or more configuration parameters of a cell. The one ormore configuration parameters may indicate one or more BFD parameters ofa downlink BWP of the cell and one or more BFR parameters of an uplinkBWP of the cell. The one or more BFD parameters (e.g., provided byRadioLinkMonitoringConfig) may comprise at least one of: one or morefirst RSs (e.g., RadioLinkMonitoringRS) for a beam failure detection ofthe downlink BWP, a beam failure detection timer (e.g.,beamFailureDetectionTimer) and a first value (e.g.,beamFailurelnstanceMaxCount). The one or more first RSs may comprise oneor more first CSI-RSs and/or one or more first SSB/PBCHs. The one ormore BFR parameters (e.g., provided by BeamFailureRecoveryConfig) maycomprise at least one of: one or more second RSs (e.g.,CandidateBeamRSList), a first search space set (e.g.,recoverySearchSpaceID) linked to a second CORESET, one or more BFRQresources (e.g., PRACH-ResourceDedicatedBFR of the candidateBeamRSList),a configured response window, and a BFR timer. The one or more secondRSs may comprise one or more second CSI-RSs and/or one or more secondSSB/PBCHs. The one or more BFR parameters may further indicate anassociation (e.g., one-to-one) between each of the one or more secondRSs and each of the one or more BFRQ resources. The one or moreconfiguration parameters may further indicate a first CORESET of thedownlink BWP.

At time T₁ 3004, the wireless device 3010 may determine a beam failureinstance, for example, based on a beam failure instance counterassociated with the cell reaching a value. A beam failure instanceindication may be provided to the wireless device 3010. The beam failureinstance indication may comprise assessing the one or more first RSs ofthe cell with radio quality less than a first threshold. The firstthreshold may be based on hypothetical BLER, RSRP, RSRQ, or SINR. Thefirst threshold may be configured by the one or more configurationparameters.

At time T₁ 3004, the wireless device 3010 may initiate a random accessprocedure for the beam failure recovery of the cell, for example, afteror in response to determining that beam failure instance counter,associated with the cell, has reached a maximum quantity of beam failureinstance indications. The wireless device 3010 may select a RS, from theone or more second RSs, for example, after or in response to initiatingthe random access procedure for the beam failure recovery. The selectedRS may be associated with a BFRQ resource, which may be one of one ormore BFRQ resources. The BFRQ resource may comprise at least onepreamble and at least one channel resource. The at least one channelresource may comprise one or more time resources and/or one or morefrequency resources. The selected RS may have a radio quality greaterthan a second threshold. The second threshold may be based on L1-RSRP,RSRQ, hypothetical BLER, or SINR. The second threshold may be configuredby the one or more configuration parameters. At time T₁ 3004, thewireless device 3010 may transmit the preamble via the at least onechannel resource, for example, after or in response to selecting the RS.

At time T1 3004, the wireless device 3010 may determine a beam failureinstance, for example, based on a beam failure instance counterassociated with the downlink BWP of the cell reaching a first value. Abeam failure instance indication may be provided by the wireless device3010. The beam failure instance indication may comprise assessing theone or more first RSs with a radio quality less than a first threshold.The first threshold may be based on hypothetical BLER, RSRP, RSRQ, orSINR. The first threshold may be configured by the one or moreconfiguration parameters. The wireless device 3010 may initiate a randomaccess procedure for the BFR of the downlink BWP of the cell, forexample, after or in response to determining that the beam failureinstance has occurred. The wireless device 3010 may start the BFR timer(if configured), for example, after or in response to initiating therandom access procedure for the beam failure recovery. The wirelessdevice 3010 may select a RS, from the one or more second RSs, forexample, after or in response to initiating the random access procedurefor the beam failure recovery. The selected RS may be associated with aBFRQ resource. The BFRQ resource may be one of one or more BFRQresources. The BFRQ resource may comprise at least one preamble and atleast one channel resource on the uplink BWP. The at least one channelresource may comprise one or more time resources and/or one or morefrequency resources. The selected RS may have a radio quality greaterthan a second threshold. The second threshold may be based on L1-RSRP,RSRQ, hypothetical BLER, or SINR. The second threshold may be configuredby the one or more configuration parameters. At time T₁ 3004, thewireless device 3010 may transmit the preamble via the at least onechannel resource, for example, after or in response to selecting the RS.

The wireless device 3010 may monitor (e.g. between time T₁ 3004 and T₃3008), based on the selected RS, a second PDCCH message in the secondCORESET for a second DCI, for example, after or in response totransmitting the preamble in the configured window. A second DM-RSantenna port for the second PDCCH message in the second CORESET may bequasi co-located (e.g., QCL-TypeD) with the selected RS.

Between time T₁ 3004 and T₃ 3008, the wireless device 3010 may receive ahigher layer (e.g., RRC) message on the second search space setassociated with the at least one of the one or more CORESETs (e.g.,other than the BFR CORESET) of the cell, for example, if the randomaccess procedure for the beam failure recovery of the configureddownlink BWP of the cell is ongoing. The higher layer message may betransmitted, by the base station 3020, and may comprise, or reconfigure,at least one of the parameters in the one or more BFR configurationparameters for the cell. A value of the at least one of the parametersmay be different from a second value provided in the one or more BFRconfiguration parameters initially. The wireless device 3010 mayreconfigure at least one of the parameters with the value, for example,based on the value being different. At least one of the parameters mayreconfigure at least one of the one or more first RSs (e.g.,RadioLinkMonitoringRS) of the configured downlink BWP. The at least oneof the one or more first RSs may be used to monitor a beam failuredetection of the configured downlink BWP. The wireless device 3010 maymeasure radio link quality of at least one of the one or more first RSs(e.g., failureDetectionResources) for a beam failure detection (e.g., ofthe configured downlink BWP of the cell). The wireless device 3010 mayreset the first beam failure counter (e.g., BFI_COUNTER) of theconfigured downlink BWP if the random access procedure for the beamfailure recovery of the configured downlink BWP of the cell is ongoing,for example, after or in response to receiving the higher layer messagecomprising, or reconfiguring, the at least one of the one or more firstRSs.

At time T₂ 3006, the wireless device 3010 may receive, from the basestation 3020, one or more second messages while the random accessprocedure is ongoing. The one or more second messages may comprise oneor more BFD parameters and/or one or more BFR parameters. The wirelessdevice 3010 may stop (e.g., abort, terminate, cease, halt, etc.) therandom access procedure for the BFR of the downlink BWP, for example,based on the one or more second messages comprising at least one of theone or more BFD parameters and/or at least one of the one or more BFRparameters. Additionally, or alternatively, the wireless device 3010 maystop (e.g., abort, terminate, cease, halt, etc.) the random accessprocedure for the BFR of the downlink BWP, for example, based on the oneor more second messages reconfiguring at least one of the one or moreBFD parameters and/or at least one of the one or more BFR parameters.The wireless device 3010 may also stop the BFR timer, for example, afteror in response to stopping (e.g., aborting, terminating, ceasing,halting, etc.) the random access procedure for the BFR of the downlinkBWP. By stopping (e.g., aborting, terminating, ceasing, halting, etc.)the random access procedure for the BFR of the downlink BWP, thewireless device 3010 may recover from the beam failure more quickly andconsume less power while recovering from the beam failure.

At time T₂ 3006, the wireless device 3010 may stop (e.g., abort,terminate, cease, halt, etc.) the random access procedure for the beamfailure recovery if the random access procedure for the beam failurerecovery of the configured downlink BWP of the cell is ongoing, forexample, after or in response to receiving the higher layer messagecomprising, or reconfiguring, the at least one of the one or more firstRSrandom access. At least one of the parameters may reconfigure thefirst beam failure detection timer (e.g., beamFailureDetectionTimer)and/or the first value (e.g., beamFailurelnstanceMaxCount) for theconfigured downlink BWP of the cell. The wireless device 3010 may stop(e.g., abort, terminate, cease, halt, etc.) the random access procedurefor the beam failure recovery if the random access procedure for thebeam failure recovery of the configured downlink BWP of the cell isongoing, for example, after or in response to receiving the higher layermessage comprising, or reconfiguring, the first beam failure detectiontimer and/or the first value. At least one of the parameters mayreconfigure the one or more second RSs (e.g., (e.g.,candidateBeamRSList) and/or the one or more BFRQ resources (e.g.,PRACH-ResourceDedicatedBFR of the candidateBeamRSList) on the configureduplink BWP.

The wireless device 3010 may stop (e.g., abort, terminate, cease, halt,etc.) the random access procedure for the beam failure recovery if therandom access procedure for the beam failure recovery of the configureddownlink BWP of the cell is ongoing, for example, after or in responseto receiving the higher layer message comprising, or reconfiguring, theone or more second RSs and/or the one or more BFRQ resources. At leastone of the parameters may reconfigure the search space set (e.g.,recoverySearchSpaceId) associated with the BFR CORESET on the configureduplink BWP. The wireless device 3010 may stop (e.g. abort) the randomaccess procedure for the beam failure recovery if the random accessprocedure for the beam failure recovery of the configured downlink BWPof the cell is ongoing, for example, after or in response to receivingthe higher layer message comprising, or reconfiguring, the search spaceset. By stopping (e.g., aborting, terminating, ceasing, halting, etc.)the random access procedure, the wireless device 3010 may recover fromthe beam failure more quickly and consume less power while doing so. Thewireless device 3010 (e.g., a physical layer of the wireless device3010) may start assessing a radio link quality of at least one of theone or more first RSs against the first threshold (e.g.,rlmInSyncOutOfSyncThreshold), for example, after or in response tostopping the random access procedure for the beam failure recovery orresetting the first beam failure counter.

At time T₂ 3006, the wireless device 3010 may stop monitoring for theBFR response if the random access procedure for the beam failurerecovery of the configured downlink BWP of the cell is ongoing, forexample, after or in response to receiving the higher layer messagecomprising, or reconfiguring, the search space set (e.g., within theconfigured response window). Monitoring for the BFR response maycomprise monitoring at least one second PDCCH reception in the BFRCORESET for a DCI (e.g. a downlink assignment or an uplink grant). Thewireless device 3010 may stop the configured response window, forexample, after or in response to stopping the monitoring for the BFRresponse. The wireless device 3010 may stop the beam failure recoverytimer (if configured), reset the first beam failure detection timer(e.g., beamFailureDetectionTimer), reset the first value (e.g.,beamFailurelnstanceMaxCount) to zero, stop the configured responsewindow, determine (e.g., assume) that the random access procedure forthe beam failure recovery is successfully completed, or any combinationthereof, for example, after or in response to stopping (e.g., aborting,terminating, ceasing, halting, etc.) the random access procedure.

At time T2 3006, the wireless device 3010 may initiate, or re-initiate,a second random access procedure for the beam failure recovery of theconfigured downlink BWP, for example, based on the higher layer messagecomprising, or reconfiguring, at least one of the parameters in the oneor more BFR configuration parameters for the cell if the wireless device3010 stops (e.g., aborts, terminates, ceases, halts, etc.) the randomaccess procedure. The wireless device 3010 may initiate the secondrandom access procedure with one or more new parameters in the higherlayer message. By initiating the second random access procedure, thewireless device 3010 may recover from the beam failure more quickly andconsume less power in the process.

The wireless device 3010 may monitor (e.g., between time T₁ 3004 and T₃3008), based on the selected RS, a second PDCCH, in the second CORESET,for a second DCI, for example, after or in response to transmitting apreamble in the configured window. A second DM-RS antenna port for thesecond PDCCH message in the second CORESET may be quasi co-located(e.g., QCL-TypeD) with the selected RS. The wireless device 3010 maydetermine that a first monitoring occasion associated with the firstCORESET overlaps with a second monitoring occasion associated with thesecond CORESET in at least one symbol of the configured response window.The wireless device 3010 may determine that a first monitoring occasionassociated with the first CORESET and a second monitoring occasionassociated with the second CORESET are separated by less than an offset(e.g., Threshold-Sched-Offset) within the configured response window.The offset may be configured by the one or more configurationparameters. The wireless device 3010 may monitor, based on the selectedRS, the first PDCCH, in the first CORESET, for the first DCI, forexample, after or in response to determining that the first monitoringoccasion and the second monitoring occasion overlap or that the firstmonitoring occasion and the second monitoring occasion are separated byless than an offset. The first DM-RS antenna port for the first PDCCHmessage in the first CORESET may be quasi co-located (e.g., QCL-TypeD)with the selected RS.

At time T₃ 3008, the wireless device 3010 may detect (e.g., receive) afirst DCI via the PDCCH message in the first CORESET, for example, ifthe response window is running. The wireless device 3010 may determinethat the BFR procedure has successfully completed, for example, if thewireless device receives the first DCI via the PDCCH reception in thefirst CORESET before the response window expires. The wireless device3010 may stop the first timer, if configured, based on the BFR proceduresuccessfully being completed. The wireless device 3010 may stop theresponse window, for example, based on the BFR procedure successfullybeing completed. If the response window expires and the wireless device3010 has not yet received the DCI, the wireless device 3010 mayincrement a transmission value. The transmission value may beinitialized to a first value (e.g., 0 or any other value) before the BFRprocedure is triggered. If the transmission value indicates a value lessthan the configured maximum transmission value, the wireless device 3010may repeat one or more actions, such as a BFR signal transmission,starting the response window, monitoring the PDCCH, and/or incrementingthe transmission value, for example, if no response was received whilethe response window was running. If the transmission value indicates avalue greater than or equal to the configured maximum transmissionvalue, the wireless device 3010 may declare the BFR procedure wascompleted unsuccessfully. An unsuccessful completion of the BFRprocedure may lead to a radio link failure (RLF).

FIG. 31 shows an example flowchart of a BFR procedure. A beam failuremay be detected by a wireless device, for example, based on rapidchanges in the environment or movement of the wireless device. Awireless device may initiate a beam failure recovery procedure, forexample, after or in response to detecting the beam failure. At step3110, a wireless device may receive one or more configuration parametersfor a cell, such as a first recovery search space or a first CORESET. Instep 3120, the wireless device may detect a beam failure. The wirelessdevice may determine (e.g., assume) a beam failure, for example, if ablock error rate of PDCCH is greater than or equal to a threshold. Thewireless device may also declare a beam failure, for example based on ameasurement of a reference signal (e.g., CSI-RS or SS block) associatedwith a PDCCH TCI state. In step 3130, the wireless device may initiate afirst random access procedure for a beam failure recovery. The wirelessdevice may use the first recovery search space set received from the oneor more configuration parameters for a cell. Additionally, oralternatively, the wireless device may initiate the first random accessprocedure using the first CORESET.

In step 3140, the wireless device may receive, from a base station,second configuration parameters while the first random access procedureis underway. The second configuration parameters may include one or moreBFD parameters and/or one or more BFR parameters. Additionally, thesecond configuration parameters may include a second recovery searchspace set or a second CORESET. The wireless device may monitor forconfiguration parameters, regardless of whether the wireless device hasreceived the second configuration parameters. After receiving the secondconfiguration parameters, the wireless device may continue to monitorfor configuration parameters. If the wireless has not received secondconfiguration parameters, the wireless device may continue to monitorfor configuration parameters during the first random access procedure.If the wireless device has received second configuration parameters, thewireless device may stop (e.g. abort) the first random access procedurefor beam failure recovery in step 3150. In step 3160, the wirelessdevice may initiate a second random access procedure for the beamfailure recovery. The wireless device may use the second recovery searchspace set or the second CORESET to perform the second random accessprocedure. The second random access procedure may be completedsuccessfully, for example, if the wireless device receives a DCI in thesecond CORESET before the response window expires. The second randomaccess procedure may be unsuccessful, for example, if the wirelessdevice has not received a DCI in the second CORESET. The second randomaccess procedure may be unsuccessful, for example, if the responsewindow expires

Hereinafter, various characteristics will be highlighted in a set ofnumbered clauses or paragraphs. These characteristics are not to beinterpreted as being limiting on the invention or inventive concept, butare provided merely as a highlighting of some characteristics asdescribed herein, without suggesting a particular order of importance orrelevancy of such characteristics.

Clause 1. A method comprising receiving, by a wireless device, firstbeam failure recovery configuration parameters comprising a firstrecovery search space set for an uplink bandwidth part (BWP).

Clause 2. The method of clause 1, further comprising initiating, basedon detecting a beam failure of a downlink BWP, a first random accessprocedure for a beam failure recovery.

Clause 3. The method of any one of clauses 1-2, further comprisingreceiving, during the first random access procedure, second beam failurerecovery configuration parameters comprising a second recovery searchspace set for the uplink BWP.

Clause 4. The method of any one of clauses 1-3, further comprisingstopping, based on the receiving the second beam failure recoveryconfiguration parameters, the first random access procedure.

Clause 5. The method of any one of clauses 1-4, further comprisinginitiating, based on the second recovery search space set, a secondrandom access procedure for the beam failure recovery.

Clause 6. The method of any one of clauses 1-5, wherein the first beamfailure recovery configuration parameters comprise a first controlresource set (CORESET) linked to the first recovery search space set.

Clause 7. The method of any one of clauses 1-6, further comprising notmonitoring the first CORESET before the initiating the first randomaccess procedure for the beam failure recovery.

Clause 8. The method of any one of clauses 1-7, further comprisingmonitoring one or more CORESETs before the initiating the first randomaccess procedure for the beam failure recovery and while the firstrandom access procedure is ongoing.

Clause 9. The method of any one of clauses 1-8, further comprisingreceiving the second beam failure recovery configuration parameters in aCORESET of the one or more CORESETs.

Clause 10. The method of any one of clauses 1-9, wherein the uplink BWPand the downlink BWP are linked.

Clause 11. The method of any one of clauses 1-10, wherein the detectingthe beam failure further comprises determining, based on a number ofbeam failure instance indications being greater than or equal to athreshold, the beam failure.

Clause 12. The method of any one of clauses 1-11, wherein the thresholdcomprises a maximum number of beam failure instance indications.

Clause 13. The method of any one of clauses 1-12, wherein a beam failureinstance indication of a consecutive number of beam failure instanceindications comprises assessing one or more reference signals with radioquality lower than a threshold.

Clause 14. The method of any one of clauses 1-13, wherein the first beamfailure recovery configuration parameters further indicate one or morereference signals for the downlink BWP.

Clause 15. The method of any one of clauses 1-14, wherein the secondrecovery search space is different from the first recovery search space.

Clause 16. The method of any one of clauses 1-15, further comprisingstarting a beam failure recovery timer based on the initiating the firstrandom access procedure.

Clause 17. The method of any one of clauses 1-16, further comprisingstopping the beam failure recovery timer based on the stopping the firstrandom access procedure.

Clause 18. The method of any one of clauses 1-17, wherein the first beamfailure recovery configuration parameters further indicate a beamfailure detection timer.

Clause 19. The method of any one of clauses 1-18, further comprisingstarting a beam failure detection timer based on a beam failure instanceindication.

Clause 20. The method of any one of clauses 1 to 19, further comprisingstopping a beam failure detection timer based on stopping the firstrandom access procedure.

Clause 21. The method of any one of clauses 1-20, further comprisingmonitoring, based on the initiating the first random access procedure, adownlink control channel in a control resource set (CORESET) fordownlink control information.

Clause 22. The method of any one of clauses 1-21, further comprisingmonitoring, based on the initiating the second random access procedure,a second downlink control channel in a second CORESET for seconddownlink control information.

Clause 23. The method of any one of clauses 1-22, further comprisingstopping monitoring the first downlink control channel in a firstCORESET based on the stopping the first random access procedure.

Clause 24. The method of any one of clauses 1-23, wherein the initiatingthe second random access procedure for the beam failure recoverycomprises monitoring, for a second downlink control information, asecond downlink control channel in a second CORESET linked to the secondrecovery search space set for the second random access procedure.

Clause 25. The method of any one of clauses 1-24, further comprisingreceiving, while the second random access procedure is ongoing, thirdbeam failure recovery configuration parameters indicating one or moresecond reference signals for a beam failure detection of the downlinkBWP.

Clause 26. The method of anyone of clauses 1-25, further comprisingstopping the second random access procedure for the beam failurerecovery based on the receiving the third beam failure recoveryconfiguration parameters.

Clause 27. The method of any one of clauses 1-26, further comprisingincrementing a beam failure instance indication counter based on a beamfailure instance indication.

Clause 28. The method of any one of clauses 1-27, comprises resetting abeam failure instance indication counter based on the stopping the firstrandom access procedure for the beam failure recovery.

Clause 29. The method of any one of clauses 1-28, further comprisingreceiving, from a base station, a beam failure recovery response.

Clause 30. The method of any one of clauses 1-29, further comprisingstopping, based on the receiving the beam failure recovery response, thesecond random access procedure for the beam failure recovery.

Clause 31. A computing device comprising: one or more processors; andmemory storing instructions that, when executed, cause the computingdevice to perform the method of any one of clauses 1-30.

Clause 32. A system comprising: a first computing device configured toperform the method of any one of clauses 1-30; and a second computingdevice configured to send the first beam failure recovery configurationparameters.

Clause 33. A computer-readable medium storing instructions that, whenexecuted, cause the performance of the method of any one of clauses1-30.

Clause 34. A method comprising initiating, by a wireless device andbased on detecting a beam failure, a beam failure recovery procedure.

Clause 35. The method of clause 34, further comprising receiving, duringthe beam failure recovery procedure, a message for reconfiguring a beamfailure recovery search space.

Clause 36. The method of any one of clauses 34-35, further comprisingstopping, based on the receiving the message, the beam failure recoveryprocedure.

Clause 37. The method of any of clauses 34-36, further comprisinginitiating, based on the stopping the beam failure recovery procedure, asecond beam failure recovery procedure.

Clause 38. The method of any one of clauses 34-37, wherein the secondbeam failure recovery procedure comprises a random access procedure.

Clause 39. The method of any one of clauses 34-38, further comprisingdetermining, based on a timer expiring, that the second beam failurerecovery procedure is unsuccessful.

Clause 40. The method of any one of clauses 34-39, further comprisingre-initiating the second beam failure recovery procedure.

Clause 41. The method of any one of clauses 34-40, wherein the receivingthe message further comprises monitoring, based on the initiating thebeam failure recovery procedure, a downlink control channel in a controlresource set (CORESET) for downlink control information.

Clause 42. The method of any one of clauses 34-41, wherein the beamfailure recovery search space comprises a search space to monitor for adownlink control channel in a control resource set (CORESET) fordownlink control information.

Clause 43. The method of any one of clauses 34-42, wherein theinitiating the beam failure recovery procedure comprises initiating arandom access procedure.

Clause 44. A computing device comprising: one or more processors; andmemory storing instructions that, when executed, cause the computingdevice to perform the method of any one of clauses 34-43.

Clause 45. A system comprising: a first computing device configured toperform the method of any one of clauses 34-43; and a second computingdevice configured to send a message for reconfiguring a beam failurerecovery search space.

Clause 46. A computer-readable medium storing instructions that, whenexecuted, cause the performance of the method of any one of clauses34-43.

Clause 47. A method comprising initiating, by a wireless device andbased on detecting a beam failure, a beam failure recovery procedure.

Clause 48. The method of clause 47, further comprising receiving, duringthe beam failure recovery procedure, one or more beam failure recoveryconfiguration parameters for reconfiguring one or more beam failuredetection beams.

Clause 49. The method of any one of clauses 47-48, further comprisingstopping, based on the reconfiguring one or more beam failure detectionbeams, the beam failure recovery procedure.

Clause 50. The method of any one of clauses 47-49, further comprisinginitiating, based on the stopping the beam failure recovery procedure, asecond beam failure recovery procedure.

Clause 51. The method of any one of clauses 47-50, further comprisingcompleting, based on receiving a beam failure recovery response, thesecond beam failure recovery procedure.

Clause 52. The method of any one of clauses 47-51, wherein the detectingthe beam failure further comprises receiving, from a physical layer ofthe wireless device, a beam failure instance indication.

Clause 53. The method of any one of clauses 47-52, wherein the detectingthe beam failure further comprises starting, based on receiving the beamfailure instance indication, a timer.

Clause 54. The method of any one of clauses 47-53, wherein the receivingone or more beam failure recovery configuration parameters furthercomprises monitoring, based on the initiating the beam failure recoveryprocedure, a downlink control channel in a control resource set(CORESET) for downlink control information.

Clause 55. A computing device comprising: one or more processors; andmemory storing instructions that, when executed, cause the computingdevice to perform the method of any one of clauses 47-53.

Clause 56. A system comprising: a first computing device configured toperform the method of any one of clauses 47-53; and a second computingdevice configured to send the one or more beam failure recoveryconfiguration parameters for reconfiguring one or more beam failuredetection beams.

Clause [57]. A computer-readable medium storing instructions that, whenexecuted, cause the performance of the method of any one of clauses47-53.

FIG. 32 shows example elements of a computing device that may be used toimplement any of the various devices described herein, including, e.g.,the base station 122A and/or 122B, the wireless device 110 (e.g., 110Aand/or 110B), or any other base station, wireless device, or computingdevice described herein. The computing device 3200 may include one ormore processors 3201, which may execute instructions stored in therandom access memory (RAM) 3203, the removable media 3204 (such as aUniversal Serial Bus (USB) drive, compact disk (CD) or digital versatiledisk (DVD), or floppy disk drive), or any other desired storage medium.Instructions may also be stored in an attached (or internal) hard drive3205. The computing device 3200 may also include a security processor(not shown), which may execute instructions of one or more computerprograms to monitor the processes executing on the processor 3201 andany process that requests access to any hardware and/or softwarecomponents of the computing device 3200 (e.g., ROM 3202, RAM 3203, theremovable media 3204, the hard drive 3205, the device controller 3207, anetwork interface 3209, a GPS 3211, a Bluetooth interface 3212, a WiFiinterface 3213, etc.). The computing device 3200 may include one or moreoutput devices, such as the display 3206 (e.g., a screen, a displaydevice, a monitor, a television, etc.), and may include one or moreoutput device controllers 3207, such as a video processor. There mayalso be one or more user input devices 3208, such as a remote control,keyboard, mouse, touch screen, microphone, etc. The computing device3200 may also include one or more network interfaces, such as a networkinterface 3209, which may be a wired interface, a wireless interface, ora combination of the two. The network interface 3209 may provide aninterface for the computing device 3200 to communicate with a network3210 (e.g., a RAN, or any other network). The network interface 3209 mayinclude a modem (e.g., a cable modem), and the external network 3210 mayinclude communication links, an external network, an in-home network, aprovider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. Additionally, the computing device 3200 may include alocation-detecting device, such as a global positioning system (GPS)microprocessor 3211, which may be configured to receive and processglobal positioning signals and determine, with possible assistance froman external server and antenna, a geographic position of the computingdevice 3200.

The example in FIG. 32 may be a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 3200 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 3201, ROM storage 3202, display 3206, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 32.Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

The disclosed mechanisms herein may be performed if certain criteria aremet, for example, in a wireless device, a base station, a radioenvironment, a network, a combination of the above, and/or the like.Example criteria may be based on, for example, wireless device and/ornetwork node configurations, traffic load, initial system set up, packetsizes, traffic characteristics, a combination of the above, and/or thelike. If the one or more criteria are met, various examples may be used.It may be possible to implement examples that selectively implementdisclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. A basestation communicating with a plurality of wireless devices may refer toa base station communicating with a subset of the total wireless devicesin a coverage area. Wireless devices referred to herein may correspondto a plurality of wireless devices of a particular LTE or 5G releasewith a given capability and in a given sector of a base station. Aplurality of wireless devices may refer to a selected plurality ofwireless devices, and/or a subset of total wireless devices in acoverage area. Such devices may operate, function, and/or perform basedon or according to drawings and/or descriptions herein, and/or the like.There may be a plurality of base stations or a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices and/or basestations perform based on older releases of LTE or 5G technology.

One or more features described herein may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features described herein, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(e.g., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or Lab VIEWMathScript.Additionally, or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above-mentioned technologiesmay be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a wireless device, a base station, andthe like) to allow operation of multi-carrier communications describedherein. The device, or one or more devices such as in a system, mayinclude one or more processors, memory, interfaces, and/or the like.Other examples may comprise communication networks comprising devicessuch as base stations, wireless devices or user equipment (wirelessdevice), servers, switches, antennas, and/or the like. A network maycomprise any wireless technology, including but not limited to,cellular, wireless, WiFi, 4G, 5G, any generation of 3GPP or othercellular standard or recommendation, wireless local area networks,wireless personal area networks, wireless ad hoc networks, wirelessmetropolitan area networks, wireless wide area networks, global areanetworks, space networks, and any other network using wirelesscommunications. Any device (e.g., a wireless device, a base station, orany other device) or combination of devices may be used to perform anycombination of one or more of steps described herein, including, forexample, any complementary step or steps of one or more of the abovesteps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the descriptions herein.Accordingly, the foregoing description is by way of example only, and isnot limiting.

What is claimed is:
 1. A method comprising: based on a detected beamfailure, sending, by a wireless device, a first message associated witha first beam failure recovery procedure; before receiving a responseassociated with the first beam failure recovery procedure, receiving asecond message for reconfiguring at least one beam failure recoveryparameter of an uplink bandwidth part (BWP) associated with a downlinkBWP, wherein the at least one beam failure recovery parameter indicatesa recovery search space associated with the downlink BWP; based on thereceiving the second message, sending a third message associated with asecond beam failure recovery procedure; and receiving, via a controlresource set associated with the recovery search space, a responseassociated with the second beam failure recovery procedure.
 2. Themethod of claim 1, further comprising: after the sending the thirdmessage, starting a timer; and monitoring, during a time that the timeris running, for the response associated with the second beam failurerecovery procedure.
 3. The method of claim 1, wherein the second beamfailure recovery procedure comprises a random access procedure for beamfailure recovery.
 4. The method of claim 1, further comprising:determining, based on a timer expiring, that the second beam failurerecovery procedure is unsuccessful; and sending a fourth messageassociated with the second beam failure recovery procedure.
 5. Themethod of claim 1, further comprising: monitoring, after the sending thefirst message and for the response associated with the first beamfailure recovery procedure, a downlink control channel in a controlresource set; and stopping, based on the receiving the second message,the monitoring the downlink control channel.
 6. The method of claim 1,wherein the recovery search space comprises a search space to monitor,for the response associated with the second beam failure recoveryprocedure, a downlink control channel in the control resource setassociated with the recovery search space.
 7. The method of claim 1,wherein the uplink BWP is an active uplink BWP linked to the downlinkBWP.
 8. The method of claim 1, further comprising based on the receivingthe second message: stopping the first beam failure recovery procedure;and initiating the second beam failure recovery procedure.
 9. A methodcomprising: receiving, by a base station, a first message associatedwith a first beam failure recovery procedure; before sending a responseassociated with the first beam failure recovery procedure, sending asecond message for reconfiguring at least one beam failure recoveryparameter of an uplink bandwidth part (BWP) associated with a downlinkBWP, wherein the at least one beam failure recovery parameter indicatesa recovery search space associated with the downlink BWP; after thesending the second message, receiving a third message associated with asecond beam failure recovery procedure; and sending, via a controlresource set associated with the recovery search space, a responseassociated with the second beam failure recovery procedure.
 10. Themethod of claim 9, further comprising: after the receiving the thirdmessage, sending, during a response window, the response associated withthe second beam failure recovery procedure.
 11. The method of claim 9,wherein the second beam failure recovery procedure comprises a randomaccess procedure for beam failure recovery.
 12. The method of claim 9,further comprising: after sending the response associated with thesecond beam failure recovery procedure, receiving a fourth messageassociated with the second beam failure recovery procedure; and sending,based on the fourth message and via the control resource set associatedwith the recovery search space, a second response associated with thesecond beam failure recovery procedure.
 13. The method of claim 9,wherein the recovery search space comprises a search space to monitor,for the response associated with the second beam failure recoveryprocedure, a downlink control channel in the control resource setassociated with the recovery search space.
 14. The method of claim 9,wherein the uplink BWP is an active uplink BWP linked to the downlinkBWP.
 15. The method of claim 9, further comprising determining to sendthe second message instead of sending the response associated with thefirst beam failure recovery procedure.
 16. The method of claim 9,further comprising: stopping the first beam failure recovery procedure;and initiating, based on the receiving the third message, the secondbeam failure recovery procedure.
 17. A wireless device comprising: oneor more processors; and memory storing instructions that, when executedby the one or more processors, cause the wireless device to: based on adetected beam failure, send a first message associated with a first beamfailure recovery procedure; before receiving a response associated withthe first beam failure recovery procedure, receive a second message forreconfiguring at least one beam failure recovery parameter of an uplinkbandwidth part (BWP) associated with a downlink BWP, wherein the atleast one beam failure recovery parameter indicates a recovery searchspace associated with the downlink BWP; based on receiving the secondmessage, send a third message associated with a second beam failurerecovery procedure; and receive, via a control resource set associatedwith the recovery search space, a response associated with the secondbeam failure recovery procedure.
 18. The wireless device of claim 17,wherein the instructions, when executed by the one or more processors,cause the wireless device to: after sending the third message, start atimer; and monitor, during a time that the timer is running, for theresponse associated with the second beam failure recovery procedure. 19.The wireless device of claim 17, wherein the second beam failurerecovery procedure comprises a random access procedure for beam failurerecovery.
 20. The wireless device of claim 17, wherein the instructions,when executed by the one or more processors, cause the wireless deviceto: determine, based on a timer expiring, that the second beam failurerecovery procedure is unsuccessful; and send a fourth message associatedwith the second beam failure recovery procedure.
 21. The wireless deviceof claim 17, wherein the instructions, when executed by the one or moreprocessors, cause the wireless device to: monitor, after sending thefirst message and for the response associated with the first beamfailure recovery procedure, a downlink control channel in a controlresource set; and stop, based on receiving the second message,monitoring the downlink control channel.
 22. The wireless device ofclaim 17, wherein the recovery search space comprises a search space tomonitor, for the response associated with the second beam failurerecovery procedure, a downlink control channel in the control resourceset associated with the recovery search space.
 23. The wireless deviceof claim 17, wherein the uplink BWP is an active uplink BWP linked tothe downlink BWP.
 24. The wireless device of claim 17, wherein theinstructions, when executed by the one or more processors, cause thewireless device to: based on receiving the second message: stop thefirst beam failure recovery procedure; and initiate the second beamfailure recovery procedure.
 25. A base station comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the base station to: receive a firstmessage associated with a first beam failure recovery procedure; beforesending a response associated with the first beam failure recoveryprocedure, send a second message for reconfiguring at least one beamfailure recovery parameter of an uplink bandwidth part (BWP) associatedwith a downlink BWP, wherein the at least one beam failure recoveryparameter indicates a recovery search space associated with the downlinkBWP; after sending the second message, receive a third messageassociated with a second beam failure recovery procedure; and send, viaa control resource set associated with the recovery search space, aresponse associated with the second beam failure recovery procedure. 26.The base station of claim 25, wherein the instructions, when executed bythe one or more processors, cause the base station to: after receivingthe third message, send, during a response window, the responseassociated with the second beam failure recovery procedure.
 27. The basestation of claim 25, wherein the second beam failure recovery procedurecomprises a random access procedure for beam failure recovery.
 28. Thebase station of claim 25, wherein the instructions, when executed by theone or more processors, cause the base station to: after sending theresponse associated with the second beam failure recovery procedure,receive a fourth message associated with the second beam failurerecovery procedure; and send, based on the fourth message and via thecontrol resource set associated with the recovery search space, a secondresponse associated with the second beam failure recovery procedure. 29.The base station of claim 25, wherein the recovery search spacecomprises a search space to monitor, for the response associated withthe second beam failure recovery procedure, a downlink control channelin the control resource set associated with the recovery search space.30. The base station of claim 25, wherein the uplink BWP is an activeuplink BWP linked to the downlink BWP.
 31. The base station of claim 25,wherein the instructions, when executed by the one or more processors,cause the base station to determine to send the second message insteadof sending the response associated with the first beam failure recoveryprocedure.
 32. The base station of claim 25, wherein the instructions,when executed by the one or more processors, cause the base station to:stop the first beam failure recovery procedure; and initiate, based onreceiving the third message, the second beam failure recovery procedure.